BIZTRAC BETA
Rental and operating of own or leased real estate

HVÅS AS

Org. no. 919152273 Limited company (AS) Østre Toten Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −342,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−342k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

HVÅS AS is registered as a limited company in Østre Toten, Innlandet with organisation number 919152273. 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: “Drive kjøp, salg, utvikling og utleie av eiendom. Selskapet skal også kunne investere i andre selskaper og drive annen salgsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK −342,000

Financial health · 2025

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

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

Who owns HVÅS AS?

PER HÅKON HVEEM
HVÅS AS
NOK 0 rev. · NOK −14,000 profit

HVÅS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HVÅS AS

Who owns HVÅS AS?

PER HÅKON HVEEM is the largest registered owner, with 50.0%.

What is the revenue of HVÅS AS?

HVÅS AS had revenue of NOK 0 in 2025.

Who is the general manager of HVÅS AS?

Erland Åslund is registered as general manager of HVÅS AS.

Where is HVÅS AS based?

HVÅS AS has its business address in Lena.

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.