BIZTRAC BETA
Rental and operating of own or leased real estate

HATVIK AS ÅSANE

Org. no. 929882768 Limited company (AS) Bergen Incorporated 1978 Active
Ownership graph ↗
Operating profit NOK −79,000
Equity NOK 192,000
Incorporated 1978
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−79k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HATVIK AS ÅSANE is registered as a limited company in Bergen, Vestland with organisation number 929882768. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1978. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Eie og drive fast eiendom samt ha deltakerinteresser i andre selskaper og alt hva herved står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −79,000
Equity
NOK 192,000
Est. value
NOK 175,000

Financial health · 2024

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.7%
Not satisfactory
Equity as a share of total capital

Who owns HATVIK AS ÅSANE?

ALEXANDER STOKKE WIEDERSTRØM
HATVIK AS ÅSANE
· NOK −79,000 profit

HATVIK AS ÅSANE has 1 registered shareholder:

All shareholders and roles →

Which companies does HATVIK AS ÅSANE own?

HATVIK AS ÅSANE holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HATVIK AS ÅSANE

Who owns HATVIK AS ÅSANE?

ALEXANDER STOKKE WIEDERSTRØM is the largest registered owner, with 100.0%.

Who is the general manager of HATVIK AS ÅSANE?

Alexander Stokke Wiederstrøm is registered as general manager of HATVIK AS ÅSANE.

Where is HATVIK AS ÅSANE based?

HATVIK AS ÅSANE has its business address in Bergen.

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.