biztrac. BETA
COMPANY REGISTER PROFILE
928355055 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

LAKKEGATA EIENDOM AS

Org. no. 928355055 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 300,000
Operating profit NOK 171,000
Equity NOK −120,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−120k kr).

LAKKEGATA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 928355055. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsforvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK 171,000 in operating profit.

Key figures · 2025

Revenue
NOK 300,000
▼ −12 %
Operating profit
NOK 171,000
▼ −29 %
Equity
NOK −120,000
▼ −108129 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
2.17
Very good
Current assets ÷ current liabilities
Profitability
4.3%
Weak
Return on total assets
Solidity
-2.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LAKKEGATA EIENDOM AS?

LAKKEGATA EIENDOM AS
NOK 300,000 rev. · NOK 171,000 profit

LAKKEGATA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAKKEGATA EIENDOM AS

Who owns LAKKEGATA EIENDOM AS?

SVAI OSLO AS is the largest registered owner, with 100.0%.

What is the revenue of LAKKEGATA EIENDOM AS?

LAKKEGATA EIENDOM AS had revenue of NOK 300,000 in 2025.

Where is LAKKEGATA EIENDOM AS based?

LAKKEGATA 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 03.10.2026.

Report a problem

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