---
title: "Utility Connect B.V.: MCC 204 MNC 66"
mcc: "204"
mnc: "66"
plmn: "20466"
operator: "Utility Connect B.V."
country: "Netherlands"
country_iso: "NL"
region: "Europe"
technologies: ["2G"]
updated: "2025-04-09"
canonical: "https://mcc-mnc.org/networks/204_66"
---

# Utility Connect B.V.: MCC 204, MNC 66 (Netherlands)

**Utility Connect B.V.** is a mobile network in [Netherlands](https://mcc-mnc.org/countries/netherlands.md) (Europe), identified by MCC **204** and MNC **66**: PLMN ID 20466, also written 204-66 or 204 66. It runs 2G.

## Identifiers

| Field | Value |
|---|---|
| MCC (Mobile Country Code) | 204 |
| MNC (Mobile Network Code) | 66 |
| PLMN ID (MCC+MNC) | 20466 |
| TADIG code | — |
| Brand | — |
| Operator | Utility Connect B.V. |
| Country | Netherlands (NL) |
| Region | Europe |
| Dialling code | — |
| Technologies | 2G |
| Last updated | 2025-04-09 |

## Technologies & bands

| Generation | Bands | Measured cells |
|---|---|---|
| 2G | [CDMA 450](https://mcc-mnc.org/coverage/cdma_450.md) | — |

## Voice & calling services

| Service | Status | Source |
|---|---|---|
| VoLTE | Unknown | — |
| VoWiFi | Unknown | — |
| ViLTE | Unknown | — |
| VoNR | Unknown | — |

A service not marked Supported or Not supported is unknown: no data either way, not a sign that the network lacks it.

## About Utility Connect B.V.

Utility Connect B.V. is a Dutch mobile network operator providing services throughout the Netherlands. Operating under Mobile Country Code (MCC) 204, which identifies the Netherlands, and Mobile Network Code (MNC) 66, Utility Connect focuses on [specify their specialization - e.g., IoT solutions, private networks, specific industries]. They are a relative newcomer to the Dutch telecommunications landscape, which is dominated by larger players like KPN, VodafoneZiggo, and T-Mobile Netherlands, offering an alternative for businesses or consumers seeking [mention their unique selling point - e.g., niche coverage, specialized services, competitive pricing].

Unlike the aforementioned publicly accessible mobile providers, Utility Connect B.V. primarily focuses on providing [mention their focus, e.g. M2M IoT solutions], often building bespoke networks for applications such as [give examples, e.g. Smart metering, logistics tracking, etc]. Their MCC and MNC numbers are essential in the configuration of devices that connect to their network, enabling them to be uniquely identified and billed correctly. While widespread consumer adoption might not be their primary goal, Utility Connect plays a vital role in the evolving Dutch technological infrastructure by supporting the increasing demand of IoT throughout the country.

## Other networks in Netherlands

| MCC | MNC | Network | TADIG |
|---|---|---|---|
| 204 | 01 | [RadioAccess Network Services](https://mcc-mnc.org/networks/204_01.md) | — |
| 204 | 02 | [Tele2](https://mcc-mnc.org/networks/204_02.md) | — |
| 204 | 03 | [Voiceworks](https://mcc-mnc.org/networks/204_03.md) | — |
| 204 | 04 | [Vodafone](https://mcc-mnc.org/networks/204_04.md) | NLDLT |
| 204 | 05 | [Elephant Talk Communications Premium Rate Services](https://mcc-mnc.org/networks/204_05.md) | — |
| 204 | 06 | [Vectone Mobile](https://mcc-mnc.org/networks/204_06.md) | — |
| 204 | 07 | [Teleena (MVNE)](https://mcc-mnc.org/networks/204_07.md) | — |
| 204 | 08 | [KPN](https://mcc-mnc.org/networks/204_08.md) | NLDPT |
| 204 | 09 | [Lycamobile](https://mcc-mnc.org/networks/204_09.md) | — |
| 204 | 10 | [KPN](https://mcc-mnc.org/networks/204_10.md) | — |
| 204 | 11 | [VoipIT B.V.](https://mcc-mnc.org/networks/204_11.md) | — |
| 204 | 12 | [Telfort](https://mcc-mnc.org/networks/204_12.md) | — |
| 204 | 13 | [Unica Installatietechniek B.V.](https://mcc-mnc.org/networks/204_13.md) | — |
| 204 | 14 | [6GMOBILE B.V.](https://mcc-mnc.org/networks/204_14.md) | — |
| 204 | 15 | [Ziggo](https://mcc-mnc.org/networks/204_15.md) | — |
| 204 | 16 | [T-Mobile BEN](https://mcc-mnc.org/networks/204_16.md) | NLDPN |
| 204 | 17 | [Intercity Zakelijk](https://mcc-mnc.org/networks/204_17.md) | — |
| 204 | 18 | [upc](https://mcc-mnc.org/networks/204_18.md) | — |
| 204 | 19 | [Mixe Communication Solutions B.V.](https://mcc-mnc.org/networks/204_19.md) | — |
| 204 | 20 | [T-Mobile](https://mcc-mnc.org/networks/204_20.md) | NLDDT |
| 204 | 21 | [ProRail B.V.](https://mcc-mnc.org/networks/204_21.md) | — |
| 204 | 22 | [Ministerie van Defensie](https://mcc-mnc.org/networks/204_22.md) | — |
| 204 | 23 | [Wyless Nederland B.V.](https://mcc-mnc.org/networks/204_23.md) | — |
| 204 | 24 | [Private Mobility Nederland B.V.](https://mcc-mnc.org/networks/204_24.md) | — |
| 204 | 25 | [CapX B.V.](https://mcc-mnc.org/networks/204_25.md) | — |
| 204 | 26 | [SpeakUp B.V.](https://mcc-mnc.org/networks/204_26.md) | — |
| 204 | 27 | [Breezz Nederland B.V.](https://mcc-mnc.org/networks/204_27.md) | — |
| 204 | 28 | [Lancelot B.V.](https://mcc-mnc.org/networks/204_28.md) | — |
| 204 | 29 | [Private Mobile Ltd](https://mcc-mnc.org/networks/204_29.md) | — |
| 204 | 60 | [Nextgen Mobile Ltd](https://mcc-mnc.org/networks/204_60.md) | — |
| 204 | 61 | [Alcadis B.V.](https://mcc-mnc.org/networks/204_61.md) | — |
| 204 | 62 | [Voxbone](https://mcc-mnc.org/networks/204_62.md) | — |
| 204 | 64 | [Zetacom B.V.](https://mcc-mnc.org/networks/204_64.md) | — |
| 204 | 65 | [AGMS Netherlands B.V.](https://mcc-mnc.org/networks/204_65.md) | — |
| 204 | 67 | [Koning en Hartman B.V.](https://mcc-mnc.org/networks/204_67.md) | — |
| 204 | 68 | [Roamware (Netherlands) B.V.](https://mcc-mnc.org/networks/204_68.md) | — |
| 204 | 69 | [KPN Mobile The Netherlands B.V.](https://mcc-mnc.org/networks/204_69.md) | — |

---

HTML version: https://mcc-mnc.org/networks/204_66 · Index for AI agents: https://mcc-mnc.org/llms.txt · Data is community-maintained; corrections welcome on the HTML page.