BIZTRAC BETA
Rental and operating of own or leased real estate

HYLLAVEGEN 3 AS

Org. no. 928658872 Limited company (AS) Namsos Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 52,000
Operating profit NOK −26,000
Equity NOK 189,000
Incorporated 2022
Share capital NOK 60,000

Signals

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

HYLLAVEGEN 3 AS is registered as a limited company in Namsos, Trøndelag with organisation number 928658872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Drift av eiendom, herunder kjøp, salg og utleievirksomhet, og det som derved står i forbindelse, samt som eier eller deltaker gjøre andre investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 52,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 52,000
Operating profit
NOK −26,000
Equity
NOK 189,000
Est. value
NOK 207,000

Financial health · 2024

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

Who owns HYLLAVEGEN 3 AS?

NYE HUSTAD EIENDOM AS
HYLLAVEGEN 3 AS
NOK 52,000 rev. · NOK −26,000 profit

HYLLAVEGEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HYLLAVEGEN 3 AS er morselskap for 5 datterselskaper:

Frequently asked questions about HYLLAVEGEN 3 AS

Who owns HYLLAVEGEN 3 AS?

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

What is the revenue of HYLLAVEGEN 3 AS?

HYLLAVEGEN 3 AS had revenue of NOK 52,000 in 2024.

Where is HYLLAVEGEN 3 AS based?

HYLLAVEGEN 3 AS has its business address in Namsos.

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.