BIZTRAC BETA
Development of building projects

NATIVA EIENDOM AS

Org. no. 911614537 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −324,000
Equity NOK −214,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−214k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−324k kr).

NATIVA EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 911614537. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie, drift og salg av eiendom, investeringer i aksjer og andeler samt hva herved står i forbindelse, herunder deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −324,000
Equity
NOK −214,000

Financial health · 2025

Liquidity
12.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.8%
Weak
Equity as a share of total capital

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

Who owns NATIVA EIENDOM AS?

BERGENSGRUPPEN UTVIKLING AS
NATIVA EIENDOM AS
· NOK −324,000 profit

NATIVA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NATIVA EIENDOM AS own?

NATIVA EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NATIVA EIENDOM AS

Who owns NATIVA EIENDOM AS?

BERGENSGRUPPEN UTVIKLING AS is the largest registered owner, with 50.0%.

Who is the general manager of NATIVA EIENDOM AS?

Thomas Taklo is registered as general manager of NATIVA EIENDOM AS.

Where is NATIVA EIENDOM AS based?

NATIVA EIENDOM AS has its business address in Bergen.

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.