BIZTRAC BETA
Rental and operating of own or leased real estate

HAVSTAD AS

Org. no. 918051368 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 129,000
Operating profit NOK 14,000
Equity NOK −794,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−794k kr).

HAVSTAD AS is registered as a limited company in Oslo, Oslo with organisation number 918051368. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og dertil naturlig tilhørende virksomhet, samt kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 129,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 129,000
Operating profit
NOK 14,000
Equity
NOK −794,000
Est. value
NOK 95,000

Financial health · 2024

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

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

Who owns HAVSTAD AS?

FRODE GRAN SERVICE AS
HAVSTAD AS
NOK 129,000 rev. · NOK 14,000 profit

HAVSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVSTAD AS

Who owns HAVSTAD AS?

FRODE GRAN SERVICE AS is the largest registered owner, with 100.0%.

What is the revenue of HAVSTAD AS?

HAVSTAD AS had revenue of NOK 129,000 in 2024.

Who is the general manager of HAVSTAD AS?

Stian Gotfred Gran is registered as general manager of HAVSTAD AS.

Where is HAVSTAD AS based?

HAVSTAD AS has its business address in Oslo.

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.