BIZTRAC BETA
Development of building projects

TOMTEGATA 5 UTVIKLING AS

Org. no. 929846389 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 6.5m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TOMTEGATA 5 UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 929846389. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling og salg av eiendom og alt som hører derunder, samt investering og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 6.5m
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns TOMTEGATA 5 UTVIKLING AS?

BRM GRUPPEN AS
TOMTEGATA 5 UTVIKLING AS
NOK 0 rev. · NOK −10,000 profit

TOMTEGATA 5 UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOMTEGATA 5 UTVIKLING AS

Who owns TOMTEGATA 5 UTVIKLING AS?

BRM GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of TOMTEGATA 5 UTVIKLING AS?

TOMTEGATA 5 UTVIKLING AS had revenue of NOK 0 in 2025.

Where is TOMTEGATA 5 UTVIKLING AS based?

TOMTEGATA 5 UTVIKLING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.