BIZTRAC BETA
Rental and operating of own or leased real estate

SNARTEMO NÆRINGSPARK AS

Org. no. 916689195 Limited company (AS) Hægebostad Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 2.2m
Equity NOK 2.2m
Incorporated 2016
Share capital NOK 200,000

SNARTEMO NÆRINGSPARK AS is registered as a limited company in Hægebostad, Agder with organisation number 916689195. 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 200,000, divided into 100 shares. The company's stated purpose is: “Utleie av næringsbygg, utleie av maskiner og utstyr, utleie av arbeidskraft og øvrige tjenester som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 2.2m
Equity
NOK 2.2m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns SNARTEMO NÆRINGSPARK AS?

O A OLSEN DRIFT AS
SNARTEMO NÆRINGSPARK AS
NOK 3.6m rev. · NOK 2.2m profit

SNARTEMO NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNARTEMO NÆRINGSPARK AS

Who owns SNARTEMO NÆRINGSPARK AS?

O A OLSEN DRIFT AS is the largest registered owner, with 100.0%.

What is the revenue of SNARTEMO NÆRINGSPARK AS?

SNARTEMO NÆRINGSPARK AS had revenue of NOK 3.6m in 2025.

Who is the general manager of SNARTEMO NÆRINGSPARK AS?

Liv Janne Olsen is registered as general manager of SNARTEMO NÆRINGSPARK AS.

Where is SNARTEMO NÆRINGSPARK AS based?

SNARTEMO NÆRINGSPARK AS has its business address in Snartemo.

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.