BIZTRAC BETA
Support services to forestry

MIDT-TELEMARK SKOG AS

Org. no. 818028172 Limited company (AS) Midt-Telemark Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK 865,000
Equity NOK 672,000
Incorporated 2016
Employees 5
Share capital NOK 100,000

MIDT-TELEMARK SKOG AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 818028172. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Skogs- og anleggsdrift. Selskapet skal også kunne investere i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK 865,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK 865,000
Equity
NOK 672,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns MIDT-TELEMARK SKOG AS?

GHM INVEST AS
MIDT-TELEMARK SKOG AS
NOK 11.0m rev. · NOK 865,000 profit

MIDT-TELEMARK SKOG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MIDT-TELEMARK SKOG AS er morselskap for 2 datterselskaper:

Frequently asked questions about MIDT-TELEMARK SKOG AS

Who owns MIDT-TELEMARK SKOG AS?

GHM INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of MIDT-TELEMARK SKOG AS?

MIDT-TELEMARK SKOG AS had revenue of NOK 11.0m in 2024.

Who is the general manager of MIDT-TELEMARK SKOG AS?

Geir Håkon Myhre is registered as general manager of MIDT-TELEMARK SKOG AS.

Where is MIDT-TELEMARK SKOG AS based?

MIDT-TELEMARK SKOG AS has its business address in Gvarv.

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.