BIZTRAC BETA
Silviculture and other forestry activities

GLOMMEN SKOGSTJENESTER AS

Org. no. 922352461 Limited company (AS) Elverum Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 15.9m
Operating profit NOK 1.3m
Equity NOK 344,000
Incorporated 2019
Share capital NOK 250,000

GLOMMEN SKOGSTJENESTER AS is registered as a limited company in Elverum, Innlandet with organisation number 922352461. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2019. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Salg av tjenester i skogrelatert virksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 15.9m
Operating profit
NOK 1.3m
Equity
NOK 344,000
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns GLOMMEN SKOGSTJENESTER AS?

GLOMMEN MJØSEN SKOG SA
GLOMMEN SKOGSTJENESTER AS
NOK 15.9m rev. · NOK 1.3m profit

GLOMMEN SKOGSTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLOMMEN SKOGSTJENESTER AS

Who owns GLOMMEN SKOGSTJENESTER AS?

GLOMMEN MJØSEN SKOG SA is the largest registered owner, with 100.0%.

What is the revenue of GLOMMEN SKOGSTJENESTER AS?

GLOMMEN SKOGSTJENESTER AS had revenue of NOK 15.9m in 2024.

Who is the general manager of GLOMMEN SKOGSTJENESTER AS?

Christian Svenkerud is registered as general manager of GLOMMEN SKOGSTJENESTER AS.

Where is GLOMMEN SKOGSTJENESTER AS based?

GLOMMEN SKOGSTJENESTER AS has its business address in Elverum.

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.