The German regulatory context
Germany applies a general authorisation regime under the Telecommunications Act (Telekommunikationsgesetz, TKG), which transposes the European Electronic Communications Code. Most public telecoms services do not require an individual licence, but providers must comply with a sequence of obligations before and after launch.
Regulator
The Bundesnetzagentur (BNetzA) supervises electronic communications, numbering, and spectrum, and enforces the TKG.
Notification, not licence
Providers of public networks or services must notify BNetzA (Meldepflicht, TKG) before or when commencing activity. There is no individual licence for most services.
Numbering
Number ranges (geographic, mobile, non-geographic, short codes) are allocated by BNetzA and carry usage and presentation rules.
Spectrum, where relevant
Wireless and satellite services may require frequency assignment or general spectrum authorisations, coordinated through BNetzA.
What we deliver for German market entry
A structured path from regulatory classification through notification, numbering, and the security and consumer obligations that follow. Delivered in coordination with your commercial, engineering, and security teams.
Regulatory classification
Determine whether your offering is a telecommunications service, an interpersonal communications service, or out of scope, and which obligations attach to each.
BNetzA notification
Prepare and file the notification, define the activity scope, and manage the exchange with the authority through to confirmation.
Numbering & CLI
Number range applications, Right to Use, and German CLI presentation rules for voice and messaging.
Lawful interception
Framing of interception and data-access obligations under the TKG and the interception ordinance (TKUEV), ETSI interfaces, and thresholds, with your engineering team.
Emergency services
Notruf 112 / 110 obligations: caller location, routing to the competent control centre, and reliability requirements.
Consumer & transparency
Pre-contract information, contract summaries, billing transparency, and the customer-information duties under the TKG.
Privacy
Telecoms privacy under the TTDSG alongside GDPR: traffic and location data, consent, and retention boundaries.
Security & NIS2
Network and information security obligations and NIS2 framing, mapped to the regulatory dimension and coordinated with your security function.
How a market-entry engagement runs
A scoped path, typically eight to twelve weeks to a compliant launch position, depending on numbering and interception scope.
Scoping & classification
Confirm the service model, classify it under the TKG, and map the applicable obligations. Output: an obligation map and a launch checklist.
Notification & numbering
File the BNetzA notification and any number-range applications. Manage authority correspondence to confirmation.
Security & interception readiness
Frame lawful interception, data access, and security obligations, and define the operator interfaces with your engineering and security teams.
Consumer, privacy & launch
Put consumer-information, billing, emergency, and privacy obligations in place, and confirm a compliant launch position.
Working with mavam.io
Project Mandate
Scoped deliverables, fixed term. Suited to a defined market-entry programme.
Retainer
Ongoing regulatory advisory once you are live, billed monthly.
Embedded
Fractional regulatory counsel inside your team for the duration of the entry.
To discuss a German market-entry mandate, contact projects@mavam.io or visit mavam.io.