BIZTRAC BETA
Other captive investment companies

SNARUD INVEST AS

Org. no. 933079228 Limited company (AS) Hamar Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −37,000
Equity NOK −21,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−21k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−37k kr).

SNARUD INVEST AS is registered as a limited company in Hamar, Innlandet with organisation number 933079228. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −37,000
Equity
NOK −21,000

Financial health · 2025

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

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

Who owns SNARUD INVEST AS?

MIKKEL STAFSBERG SNARUD
SNARUD INVEST AS
NOK 0 rev. · NOK −37,000 profit

SNARUD INVEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SNARUD INVEST AS

Who owns SNARUD INVEST AS?

MIKKEL STAFSBERG SNARUD is the largest registered owner, with 50.0%.

What is the revenue of SNARUD INVEST AS?

SNARUD INVEST AS had revenue of NOK 0 in 2025.

Where is SNARUD INVEST AS based?

SNARUD INVEST AS has its business address in Hamar.

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.