BIZTRAC BETA
Business and other management consultancy activities

GREEN EIENDOM AS

Org. no. 893442952 Limited company (AS) Lier Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 7.3m
Incorporated 2008
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

GREEN EIENDOM AS is registered as a limited company in Lier, Buskerud with organisation number 893442952. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2008. Registered share capital is NOK 1.0m, divided into 100000 shares. The company's stated purpose is: “Konsulentvirksomhet og investeringsvirksomhet, herunder investeringer i aksjer, obligasjoner, selskapsandeler, verdipapirer, fast eiendom, utlån eller annen virksomhet, selv eller gjennom hel- eller deleide selskaper.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 7.3m
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
66.33
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns GREEN EIENDOM AS?

GUUL AS
GREEN EIENDOM AS
· NOK −1,000 profit

GREEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GREEN EIENDOM AS own?

GREEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GREEN EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about GREEN EIENDOM AS

Who owns GREEN EIENDOM AS?

GUUL AS is the largest registered owner, with 100.0%.

Who is the general manager of GREEN EIENDOM AS?

Kristian Green is registered as general manager of GREEN EIENDOM AS.

Where is GREEN EIENDOM AS based?

GREEN EIENDOM AS has its business address in Gullaug.

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.