BIZTRAC BETA
Rental and operating of own or leased real estate

HAUGERUDVEIEN AS

Org. no. 919727381 Limited company (AS) Ås Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 893,000
Equity NOK −1.1m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).

HAUGERUDVEIEN AS is registered as a limited company in Ås, Akershus with organisation number 919727381. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie, investere og drifte eiendom samt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 893,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 893,000
Equity
NOK −1.1m
Est. value
NOK 6.1m

Financial health · 2024

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

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

Who owns HAUGERUDVEIEN AS?

TGN AS
HAUGERUDVEIEN AS
NOK 7.1m rev. · NOK 893,000 profit

HAUGERUDVEIEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAUGERUDVEIEN AS

Who owns HAUGERUDVEIEN AS?

TGN AS is the largest registered owner, with 50.0%.

What is the revenue of HAUGERUDVEIEN AS?

HAUGERUDVEIEN AS had revenue of NOK 7.1m in 2024.

Where is HAUGERUDVEIEN AS based?

HAUGERUDVEIEN AS has its business address in Ås.

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.