BIZTRAC BETA
Rental and operating of own or leased real estate

BLEKKAN EIENDOM AS

Org. no. 916035551 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −51,000
Equity NOK −72.2m
Incorporated 2015
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−72,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−51k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BLEKKAN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916035551. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, aksjer, verdipapirer, fast eiendom og alt som er forbundet med dette.”.

Key figures · 2024

Operating profit
NOK −51,000
Equity
NOK −72.2m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-345.4%
Weak
Equity as a share of total capital

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

Who owns BLEKKAN EIENDOM AS?

BLEKKAN HOLDING AS
BLEKKAN EIENDOM AS
· NOK −51,000 profit

BLEKKAN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BLEKKAN EIENDOM AS own?

BLEKKAN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLEKKAN EIENDOM AS

Who owns BLEKKAN EIENDOM AS?

BLEKKAN HOLDING AS is the largest registered owner, with 60.0%.

Where is BLEKKAN EIENDOM AS based?

BLEKKAN EIENDOM AS has its business address in Trondheim.

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.