ConMet — 4 prefixes (MA-L)
Summary
- // what this is
- ConMet is registered to MAC prefix
D0:98:9Cand 3 more in the IEEE OUI database. When a device's MAC address begins withD0:98:9C, that block was registered by ConMet — the OUI identifies the maker of the network hardware, which is not always the brand on the device. - // analyst note
- Multiple OUI assignments to the same corporate address are stronger evidence of vendor substance than a bare registration, but device-type attribution here is unconfirmed — treat matches as fleet/OEM embedded electronics, not consumer IoT, until a specific product/network-interface is documented.
About this vendor.
A MAC address beginning with D0:98:9C, 14:5B:B9, 34:EE:2A, or 54:66:F9 belongs to ConMet (Consolidated Metco), a commercial-vehicle components manufacturer, typically seen on industrial fleet/OEM embedded electronics rather than consumer network gear.
ConMet is a substantial, identifiable company, not a bare single-OUI registration. It holds four separate IEEE MA-L assignments under the identical name and Vancouver, WA address, consistent with an active manufacturer that has needed repeated MAC-address block allocation over time. Founded in 1964 and owned by Amsted Industries, the company operates 16 global manufacturing facilities and maintains a detailed corporate website.
ConMet's traditional product lines — PreSet and PreSet Plus wheel hubs, brake drums, castings, and TruckWings aerodynamic fairings — are mechanical components with no obvious network interface. The company also markets an eHub/eMobility electric wheel-hub power-unit line for trailer refrigeration and electrified trucks, integrated with Carrier Transicold and Freightliner eCascadia, which is a plausible source of embedded MAC-bearing hardware, but no product documentation confirms which specific device carries these OUIs.
No FCC ID filings under ConMet or Consolidated Metco were found, and no CVEs or security advisories reference the company. A similarly-named "Wheel Hub Data Sensor" (FCC ID 2AY6OSHN01) belongs to a distinct company, Rivata Inc., with no confirmed relationship to ConMet.
- IEEE assignment
- 4 prefixes → ConMet, registered Vancouver, WA, US [Confirmed] — the IEEE MA-L registry (lines 8596, 16441, 24407, 24918)
- Registry / block size
- MA-L (24-bit OUI); 4 IEEE prefixes registered to identical name/address; no MAM or OUI-36 entries found [Confirmed] — the IEEE MA-L registry, the IEEE MA-M registry, the IEEE MA-S registry
- HQ / country
- 5701 SE Columbia Way, Vancouver, WA 98661, US [Confirmed] — the IEEE MA-L registry; https://www.conmet.com
- Company status
- active [Confirmed] — https://www.conmet.com
- Device types
- Unknown/unconfirmed — core products (wheel hubs, brake drums, castings, aero fairings) are traditionally non-networked; the eHub/eMobility electric wheel-hub line is a plausible but unverified candidate for MAC-bearing hardware[Unknown] — https://www.conmet.com/products/, https://fccid.io/search.php?q=ConMet (no ConMet hits)
- Notable products
- PreSet/PreSet Plus wheel hubs, brake drums, TruckWings aero fairings, eHub/eMobility electric wheel-hub power units [Confirmed] — https://www.conmet.com
- Verified sample prefixes (all MA-L, ConMet)
- D0:98:9C, 14:5B:B9, 34:EE:2A, 54:66:F9 [Confirmed] — the IEEE MA-L registry
- Registration date
- not published — IEEE OUI registry data carries no date metadata for MAC registrations; no third-party "date registered" value was fetched or recorded [Confirmed] — the IEEE MA-L registry
- Related vendors
- none confirmed; Rivata Inc. (FCC ID 2AY6OSHN01, "Wheel Hub Data Sensor") surfaced in the same product-category search but has no established relationship to ConMet [Unknown] — https://fccid.io/search.php?q=ConMet
- Analyst note
- Four independent MA-L assignments to the identical name/address is stronger evidence of an active industrial-electronics vendor than a bare single-OUI shell, but no product documentation confirms which ConMet hardware line carries these MACs — treat device attribution as fleet/OEM embedded electronics context, not consumer IoT, until a specific product is documented.