biztrac. BETA
COMPANY REGISTER PROFILE
936337481 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Silviculture and other forestry activities

S.G. HAGEN HOLDING AS

Org. no. 936337481 Limited company (AS) Sunnfjord Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 45,000
Incorporated 2025
Share capital NOK 50,000

Signals

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

S.G. HAGEN HOLDING AS is registered as a limited company in Sunnfjord, Vestland with organisation number 936337481. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Holdingselskap som eiger aksjer i andre aksjeselskap. Når datterselskapet tener pengar eller deler ut overskudd, blir det ført over til ditta holdingselskapet. Og reinvistering i andre aksjeselskaper.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 45,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns S.G. HAGEN HOLDING AS?

S.G. HAGEN HOLDING AS
· NOK −7,000 profit

S.G. HAGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.G. HAGEN HOLDING AS own?

S.G. HAGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S.G. HAGEN HOLDING AS

Who owns S.G. HAGEN HOLDING AS?

Sondre Grimset Hagen is the largest registered owner, with 100.0%.

Where is S.G. HAGEN HOLDING AS based?

S.G. HAGEN HOLDING AS has its business address in Førde.

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

Report a problem

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