biztrac. BETA
COMPANY REGISTER PROFILE
989077929 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BAKKEBY INVEST AS

Org. no. 989077929 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK 156,000
Equity NOK 6.5m
Incorporated 2005
Share capital NOK 100,000

BAKKEBY INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 989077929. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapet skal kunne delta i andre selskaper med økonomisk virksomhet, herunder handel med verdipapirer, samt kjøp, utleie og salg av eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK 156,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
▲ +7173 %
Operating profit
NOK 156,000
▲ +30190 %
Equity
NOK 6.5m
▲ +2 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
961.87
Very good
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns BAKKEBY INVEST AS?

BAKKEBY INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BAKKEBY INVEST AS own?

BAKKEBY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BAKKEBY INVEST AS

Who owns BAKKEBY INVEST AS?

Hans Petter Leer is the largest registered owner, with 34.0%.

What is the revenue of BAKKEBY INVEST AS?

BAKKEBY INVEST AS had revenue of NOK 160,000 in 2025.

Where is BAKKEBY INVEST AS based?

BAKKEBY INVEST 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 03.10.2026.

Report a problem

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