BIZTRAC BETA
Rental and operating of own or leased real estate

BTO EIENDOM AS

Org. no. 920040233 Limited company (AS) Kongsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 183,000
Operating profit NOK 88,000
Equity NOK 538,000
Incorporated 2017
Share capital NOK 30,000

BTO EIENDOM AS is registered as a limited company in Kongsberg, Buskerud with organisation number 920040233. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av næringsbygg, kjøp og salg av varer og tjenester, utleie, salg og kjøp av eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 183,000 in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 183,000
Operating profit
NOK 88,000
Equity
NOK 538,000
Est. value
NOK 540,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.3%
Good
Equity as a share of total capital

Who owns BTO EIENDOM AS?

BJØRN TORE ODDEN
BTO EIENDOM AS
NOK 183,000 rev. · NOK 88,000 profit

BTO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BTO EIENDOM AS own?

BTO EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BTO EIENDOM AS

Who owns BTO EIENDOM AS?

BJØRN TORE ODDEN is the largest registered owner, with 100.0%.

What is the revenue of BTO EIENDOM AS?

BTO EIENDOM AS had revenue of NOK 183,000 in 2025.

Who is the general manager of BTO EIENDOM AS?

Bjørn Tore Odden is registered as general manager of BTO EIENDOM AS.

Where is BTO EIENDOM AS based?

BTO EIENDOM AS has its business address in Kongsberg.

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.