VECOS Europe B.V. is a Dutch smart-locker company registered to ESP 237, Eindhoven, Noord-Brabant, NL 5633 AD. It holds two IEEE assignments from the same address: one MA-L (24-bit) block, prefix 5C:E6:88, and one MA-S (36-bit) block, prefix 8C:1F:64:C8:00/36 — both confirmed in the cached IEEE registry CSVs. No MA-M block exists. Vecos builds networked locker infrastructure (marketed as the Releezme system): the LBC3 locker terminal is the controller that connects to the enterprise LAN over Ethernet (dual RJ45) and bridges to an RS485 HUB backbone; the W1 HUB connection box adds BLE and 13.56 MHz RFID/NFC; and the V3/V3+ locker locks are RFID endpoints with no direct Ethernet MAC. Because only the LBC3 terminal carries a direct LAN MAC, it is the most plausible consumer of the MA-L block, with the smaller MA-S pool likely covering a variant or production run. For triage, a Vecos OUI on a corporate network is a managed workplace-IoT locker controller — apply the usual VLAN-segmentation and firmware-patch hygiene. No CVEs or public security incidents were found.
- IEEE assignment
- 2 prefixes → "VECOS Europe B.V." — MA-L 5C:E6:88, MA-S 8C:1F:64:C8:00/36, registered Eindhoven, Netherlands [Confirmed] — IEEE oui.csv (row 168) + oui36.csv (row 5798); corroborated by IEEE
manuf (lines 29921, 42040)
- Registry / block size
- one MA-L (24-bit OUI) + one MA-S (36-bit, OUI-36); no MA-M block found in mam.csv [Confirmed] — IEEE oui.csv, oui36.csv, mam.csv (cached)
- HQ / country
- ESP 237, Eindhoven, Noord-Brabant, NL 5633 AD, Netherlands (Brainport Eindhoven) [Confirmed] — IEEE registry address; corroborated vecos.com/about-us, Kompass
- Company status
- active; private company, Ardian (France) private-equity backing for international growth; operates in 60+ countries [Confirmed] — ardian.com press release, vecos.com/about-us
- Company founded
- ~1996 (vendor self-states "since 1996"); Kompass lists 1986 — treat the 1986 value as a likely database artifact, 1996 corroborated by the vendor site and multiple business databases [Likely] — vecos.com/about-us, leadiq.com (1996); gb.kompass.com (1986, conflicting)
- Device types
- networked smart-locker IoT — LBC3 locker terminal (TCP/IP over CAT5E+ Ethernet, dual RJ45; bridges LAN to RS485 HUB backbone), W1 HUB connection box (BLE + 13.56 MHz RFID/NFC), V3/V3+ locker locks (RFID/NFC endpoints, no direct Ethernet MAC) [Likely] — fccid.io/2ACYA, device.report manual 15414453, vecos.com/smart-locker-system
- Notable products
- Releezme smart-locker system; LBC3 locker terminal; HUB W1 connection box; V3 / V3+ / V3+Legic locker locks; ISO 27001-certified SaaS cloud backend (vendor-stated) [Confirmed for product line] — vecos.com/smart-locker-system, fccid.io/2ACYA
- Verified prefixes
- 5C:E6:88 (MA-L); 8C:1F:64:C8:00/36 (MA-S) [Confirmed] — IEEE oui.csv, oui36.csv
- FCC IDs (grantee code 2ACYA = Vecos Europe B.V.)
- 2ACYAV3NXP (V3 lock, NXP RFID 13.56 MHz), 2ACYAV3NXP1 (V3+ / V3+HID lock), 2ACYAW1HUB (W1 HUB, BLE+HF) [Confirmed] — fccid.io/2ACYA, fccid.io/2ACYAV3NXP1
- Security context
- no CVEs, CISA advisories, or NVD entries found for Vecos products as of 2026-06-15. UpGuard rates vecos.com web infrastructure B (738/950), noting missing security headers (no CSP/X-Frame-Options/CAA), DMARC p=none, and some open ports — these are website-infrastructure findings, not locker-device firmware. Standard corporate-IoT risk surface applies to the LBC3 (LAN-resident, outbound to Vecos SaaS); the W1 HUB BLE bonding requires a physical button press, reducing remote-bonding risk [Likely] — upguard.com/security-report/vecos-europe-bv, vecos.com
- Special note
- IEEE publishes NO assignment/registration date for 5C:E6:88 or the MA-S block (oui.csv/oui36.csv columns are only Registry, Assignment, Organization Name, Organization Address); any "date registered" from third-party lookup tools is a database artifact, not an IEEE fact. [Confirmed]
- Related vendors
- Ardian (private-equity owner); NXP / HID / Legic (RFID technology in the locks)
- Analyst note
- A Vecos OUI (5C:E6:88 or the 8C:1F:64:C8 MA-S block) on a corporate network is a managed workplace-IoT smart-locker controller — most likely an LBC3 terminal carrying the direct LAN MAC. Locker locks behind it are RFID endpoints and won't surface their own IP MAC; inventory the LBC3/HUB layer. Apply VLAN segmentation and firmware-patch hygiene as for any managed IoT.