Intertech Services AG — 3 prefixes (MA-L)

A MAC address starting AC:BA:C0, B8:87:6E, or 3C:0B:4F belongs to Intertech Services AG, a Swiss data-hosting and software-services company — these three IEEE MA-L blocks are registered to the same organization and address, but no consumer or enterprise device class is confirmed for any of them.

Intertech Services AG is a real, identifiable Swiss commercial-register entity (CHE-229.170.782) at Werftestrasse 4, 6005 Luzern, with a documented corporate history rather than a bare single-OUI shell registration. It was registered 12 January 2012 as "Yandex Zurich AG," renamed "Yandex Services AG" in May 2015, then renamed to its current name on 1 April 2022.

No product pages, hardware manuals, or device-fingerprint databases tie any of the three prefixes to a specific device type. The company's classification is data processing/hosting and computer-programming activities, so these blocks most plausibly cover internal server or data-center networking equipment rather than a shipped product line.

Current registration status is unresolved: one aggregator (northdata) states the company was terminated 27 November 2025, while another states it remains active with a most-recent-change date of 1 July 2025. Neither claim was independently confirmed against the Swiss commercial register directly, so this entry treats the status as disputed rather than settled.

IEEE assignment

3 prefixes (AC:BA:C0, B8:87:6E, 3C:0B:4F) → Intertech Services AG, registered Luzern, CH [Confirmed] — the IEEE MA-L registry (IEEE-sourced master)

Registry / block size

MA-L (24-bit OUI) x3, all same organization/address [Confirmed] — the IEEE MA-L registry, the Wireshark manufacturer database. NOTE: IEEE's public OUI data publishes NO assignment/registration date; any "date registered" on third-party tools is a database artifact, not an IEEE fact.

HQ / country

Werftestrasse 4, 6005 Luzern, Switzerland (CH) [Confirmed] — the IEEE MA-L registry; northdata.com

Company status

Disputed — one source (northdata) states terminated 27 Nov 2025; another states currently active, most recent change 1 Jul 2025. Not independently confirmed via zefix.ch (moneyhouse.ch and tiger.ch returned HTTP 403 to fetch).

[Unknown] — https://www.northdata.com/Intertech+Services+AG,+Luzern/CHE-229.170.782

Device types

none identified — no product/hardware documentation found for any of the three prefixes [Unknown] — https://maclookup.app/macaddress/3c0b4f

Notable products

none found [Unknown]

Industry

data processing and hosting services / computer programming activities [Likely] — https://www.northdata.com/Intertech+Services+AG,+Luzern/CHE-229.170.782

Verified prefixes (all MA-L, Intertech Services AG)

AC:BA:C0, B8:87:6E, 3C:0B:4F [Confirmed] — the IEEE MA-L registry (lines 14619, 22527-22528)

Corporate lineage

registered 12 Jan 2012 as "Yandex Zurich AG"; renamed "Yandex Services AG" 20/26 May 2015; renamed "Intertech Services AG" 1 April 2022 [Likely] — https://www.northdata.com/Intertech+Services+AG,+Luzern/CHE-229.170.782, https://www.monetas.ch/en/647/Firmendaten-Yandex-Services-AG.htm?subj=2214116

Third-party date caveat

maclookup.app lists an "initially registered 01 April 2022" date for 3C:0B:4F — this coincides exactly with the Yandex Services AG -> Intertech Services AG rename date, indicating it is a scrape artifact tied to the vendor-name update in a third-party feed, not an IEEE assignment date

[Likely] — https://maclookup.app/macaddress/3c0b4f

Website

not confirmed [Unknown]

Related vendors

Yandex Services AG (predecessor name, 2015-2022); Yandex Zurich AG (original name, 2012-2015) [Likely] — https://www.northdata.com/Intertech+Services+AG,+Luzern/CHE-229.170.782

Analyst note

multi-OUI, verifiable Swiss registered entity with documented corporate history (former Yandex Swiss subsidiary, renamed away from the Yandex brand April 2022) — substantive company identity, but zero product/device evidence, so treat as a services/hosting company rather than a device vendor for MAC-based inventory purposes. No evidence of malicious use of the OUI blocks was found.