BIZTRAC BETA
Support services to forestry

SOLEM SKOGSERVICE AS

Org. no. 928791858 Limited company (AS) Surnadal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 727,000
Operating profit NOK 58,000
Equity NOK 142,000
Incorporated 2022
Share capital NOK 30,000

SOLEM SKOGSERVICE AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 928791858. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skogkultur, skogrydding, faglig veiledning og arbeidsledelse, samt annen virksomhet som naturlig står i forbindelse med dette. Eventuelt deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 727,000 in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 727,000
Operating profit
NOK 58,000
Equity
NOK 142,000
Est. value
NOK 283,000

Financial health · 2025

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

Who owns SOLEM SKOGSERVICE AS?

ERLING SOLEM
SOLEM SKOGSERVICE AS
NOK 727,000 rev. · NOK 58,000 profit

SOLEM SKOGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLEM SKOGSERVICE AS

Who owns SOLEM SKOGSERVICE AS?

ERLING SOLEM is the largest registered owner, with 100.0%.

What is the revenue of SOLEM SKOGSERVICE AS?

SOLEM SKOGSERVICE AS had revenue of NOK 727,000 in 2025.

Who is the general manager of SOLEM SKOGSERVICE AS?

Erling Solem is registered as general manager of SOLEM SKOGSERVICE AS.

Where is SOLEM SKOGSERVICE AS based?

SOLEM SKOGSERVICE AS has its business address in Bæverfjord.

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.