BIZTRAC BETA
Development of building projects

GILHUSBUKTA EIENDOM AS

Org. no. 914774950 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 600,000
Incorporated 2015
Share capital NOK 186,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GILHUSBUKTA EIENDOM AS is registered as a limited company in Lier, Buskerud with organisation number 914774950. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 186,000, divided into 16190 shares. The company's stated purpose is: “Utfylling og etablering av fast land/eiendom "fjordby" i Gilhusbukta.”.

Key figures · 2025

Operating profit
NOK −61,000
Equity
NOK 600,000
Est. value
NOK 548,000

Financial health · 2025

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

Who owns GILHUSBUKTA EIENDOM AS?

IAT HOLDING AS
GILHUSBUKTA EIENDOM AS
· NOK −61,000 profit

GILHUSBUKTA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GILHUSBUKTA EIENDOM AS own?

GILHUSBUKTA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GILHUSBUKTA EIENDOM AS

Who owns GILHUSBUKTA EIENDOM AS?

IAT HOLDING AS is the largest registered owner, with 65.8%.

Who is the general manager of GILHUSBUKTA EIENDOM AS?

Ivar Andreas Tanum is registered as general manager of GILHUSBUKTA EIENDOM AS.

Where is GILHUSBUKTA EIENDOM AS based?

GILHUSBUKTA EIENDOM AS has its business address in Lierstranda.

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.