BIZTRAC BETA
Rental and operating of own or leased real estate

HUNNSVEIEN 3 AS

Org. no. 925767123 Limited company (AS) Gjøvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 803,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-25 Adresseendring registrert 2026-02-25.

HUNNSVEIEN 3 AS is registered as a limited company in Gjøvik, Innlandet with organisation number 925767123. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av fast eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 803,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 803,000
Equity
NOK 1.1m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns HUNNSVEIEN 3 AS?

ARNE HAUGOM AS
HUNNSVEIEN 3 AS
NOK 1.5m rev. · NOK 803,000 profit

HUNNSVEIEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUNNSVEIEN 3 AS

Who owns HUNNSVEIEN 3 AS?

ARNE HAUGOM AS is the largest registered owner, with 100.0%.

What is the revenue of HUNNSVEIEN 3 AS?

HUNNSVEIEN 3 AS had revenue of NOK 1.5m in 2025.

Where is HUNNSVEIEN 3 AS based?

HUNNSVEIEN 3 AS has its business address in Gjøvik.

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.