BIZTRAC BETA
Rental and operating of own or leased real estate

WILDENVEYS HAGE AS

Org. no. 989994891 Limited company (AS) Drammen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −190,000
Equity NOK 200,000
Incorporated 2006
Share capital NOK 200,000

Signals

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

WILDENVEYS HAGE AS is registered as a limited company in Drammen, Buskerud with organisation number 989994891. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og eiendomsdrift, herunder erverv, utvikling, drift, salg og utleie av fast eiendom. Det skal være anledning til å eie aksjer og andeler i andre selskaper, samt hva herved naturlig står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −190,000
Equity
NOK 200,000
Est. value
NOK 183,000

Financial health · 2024

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

Who owns WILDENVEYS HAGE AS?

ORIGO EIENDOM AS
WILDENVEYS HAGE AS
· NOK −190,000 profit

WILDENVEYS HAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WILDENVEYS HAGE AS

Who owns WILDENVEYS HAGE AS?

ORIGO EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of WILDENVEYS HAGE AS?

Tina Kalmo Pedersen is registered as general manager of WILDENVEYS HAGE AS.

Where is WILDENVEYS HAGE AS based?

WILDENVEYS HAGE AS has its business address in Drammen.

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.