BIZTRAC BETA
Uoppgitt

HÅVARD S. AS

Org. no. 919154616 Limited company (AS) Åfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 56.2m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

HÅVARD S. AS is registered as a limited company in Åfjord, Trøndelag with organisation number 919154616. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å foreta investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet, fast eiendom og annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 56.2m
Est. value
NOK 33.0m

Financial health · 2025

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

Who owns HÅVARD S. AS?

HÅVARD TINNEN STJERN
HÅVARD S. AS
NOK 0 rev. · NOK −29,000 profit

HÅVARD S. AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HÅVARD S. AS own?

HÅVARD S. AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HÅVARD S. AS

Who owns HÅVARD S. AS?

HÅVARD TINNEN STJERN is the largest registered owner, with 100.0%.

What is the revenue of HÅVARD S. AS?

HÅVARD S. AS had revenue of NOK 0 in 2025.

Where is HÅVARD S. AS based?

HÅVARD S. AS has its business address in Åfjord.

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.