BIZTRAC BETA
Rental and operating of own or leased real estate

TB24 EIENDOM AS

Org. no. 934490681 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 12.1m
Operating profit NOK −2.1m
Equity NOK 86.0m
Incorporated 2024
Share capital NOK 30,000

Signals

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

TB24 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 934490681. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet og alt hva hermed står i forbindelse samt deltakelse i andre selskaper og prosjekter med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.1m in revenue and NOK −2.1m in operating profit.

Key figures · 2025

Revenue
NOK 12.1m
Operating profit
NOK −2.1m
Equity
NOK 86.0m
Est. value
NOK 78.5m

Financial health · 2025

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

Who owns TB24 EIENDOM AS?

CLARKSONS CORE PLUS MIDCO AS
TB24 EIENDOM AS
NOK 12.1m rev. · NOK −2.1m profit

TB24 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TB24 EIENDOM AS

Who owns TB24 EIENDOM AS?

CLARKSONS CORE PLUS MIDCO AS is the largest registered owner, with 100.0%.

What is the revenue of TB24 EIENDOM AS?

TB24 EIENDOM AS had revenue of NOK 12.1m in 2025.

Where is TB24 EIENDOM AS based?

TB24 EIENDOM 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.