BIZTRAC BETA
Rental and operating of own or leased real estate

REE FORRETNINGSDRIFT AS

Org. no. 912109100 Limited company (AS) Kongsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 224,000
Operating profit NOK 59,000
Equity NOK 814,000
Incorporated 2013
Share capital NOK 225,000

REE FORRETNINGSDRIFT AS is registered as a limited company in Kongsberg, Buskerud with organisation number 912109100. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 225,000, divided into 2250 shares. The company's stated purpose is: “Fremstilling/salg/utleie av eiendom og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 224,000 in revenue and NOK 59,000 in operating profit.

Key figures · 2024

Revenue
NOK 224,000
Operating profit
NOK 59,000
Equity
NOK 814,000
Est. value
NOK 692,000

Financial health · 2024

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

Who owns REE FORRETNINGSDRIFT AS?

OLE TOM EGER
REE FORRETNINGSDRIFT AS
NOK 224,000 rev. · NOK 59,000 profit

REE FORRETNINGSDRIFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about REE FORRETNINGSDRIFT AS

Who owns REE FORRETNINGSDRIFT AS?

OLE TOM EGER is the largest registered owner, with 33.3%.

What is the revenue of REE FORRETNINGSDRIFT AS?

REE FORRETNINGSDRIFT AS had revenue of NOK 224,000 in 2024.

Where is REE FORRETNINGSDRIFT AS based?

REE FORRETNINGSDRIFT AS has its business address in Hvittingfoss.

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.