BIZTRAC BETA
COMPANY REGISTER PROFILE
934663055 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

STINE HOSTAD HOLDING AS

Org. no. 934663055 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 825,000
Incorporated 2024
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).
  • Nylig endring 2026-07-28 Aksjekapital registrert 2026-07-28.

STINE HOSTAD HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934663055. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer, kunst, samt andre aktiviteter som hører naturlig sammen med dette.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 825,000
▲ +1 %
Est. value
NOK 501,000

Financial health · 2025

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

Who owns STINE HOSTAD HOLDING AS?

STINE HOSTAD HOLDING AS
· NOK −15,000 profit

STINE HOSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STINE HOSTAD HOLDING AS own?

STINE HOSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STINE HOSTAD HOLDING AS

Who owns STINE HOSTAD HOLDING AS?

STINE HOSTAD is the largest registered owner, with 100.0%.

Who is the general manager of STINE HOSTAD HOLDING AS?

Stine Hostad is registered as general manager of STINE HOSTAD HOLDING AS.

Where is STINE HOSTAD HOLDING AS based?

STINE HOSTAD HOLDING AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.