BIZTRAC BETA
Rental and operating of own or leased real estate

HYSTADÅSEN AS

Org. no. 923947752 Limited company (AS) Sandefjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK −656,000
Equity NOK −1.2m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−656k kr).

HYSTADÅSEN AS is registered as a limited company in Sandefjord, Vestfold with organisation number 923947752. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Erverv, utvikling, vedlikehold og drift av fast eiendom samt ha økonomiske interesse i andre bedrifter og virksomheter og hva der står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK −656,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK −656,000
Equity
NOK −1.2m

Financial health · 2025

Liquidity
104.37
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-60.4%
Weak
Equity as a share of total capital

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

Who owns HYSTADÅSEN AS?

BOLIGFAG AS
HYSTADÅSEN AS
NOK 5.7m rev. · NOK −656,000 profit

HYSTADÅSEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HYSTADÅSEN AS

Who owns HYSTADÅSEN AS?

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

What is the revenue of HYSTADÅSEN AS?

HYSTADÅSEN AS had revenue of NOK 5.7m in 2025.

Where is HYSTADÅSEN AS based?

HYSTADÅSEN AS has its business address in Sandefjord.

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.