BIZTRAC BETA
Logging

MYKLEBOSTAD SKOG AS

Org. no. 923874860 Limited company (AS) Evje Og Hornnes Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 114,000
Operating profit NOK −28,000
Equity NOK 800,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

MYKLEBOSTAD SKOG AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 923874860. The business is classified under logging (NACE 02.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av leid skog, samt alt hva dermed står i forbindelse, herunder aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 114,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 114,000
Operating profit
NOK −28,000
Equity
NOK 800,000
Est. value
NOK 439,000

Financial health · 2024

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

Who owns MYKLEBOSTAD SKOG AS?

MYKLEBOSTAD AS
MYKLEBOSTAD SKOG AS
NOK 114,000 rev. · NOK −28,000 profit

MYKLEBOSTAD SKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYKLEBOSTAD SKOG AS

Who owns MYKLEBOSTAD SKOG AS?

MYKLEBOSTAD AS is the largest registered owner, with 100.0%.

What is the revenue of MYKLEBOSTAD SKOG AS?

MYKLEBOSTAD SKOG AS had revenue of NOK 114,000 in 2024.

Who is the general manager of MYKLEBOSTAD SKOG AS?

Aslak Myklebostad is registered as general manager of MYKLEBOSTAD SKOG AS.

Where is MYKLEBOSTAD SKOG AS based?

MYKLEBOSTAD SKOG AS has its business address in Evje.

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.