biztrac. BETA
COMPANY REGISTER PROFILE
935487579 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

SKOG OG MASKINDRIFT AS

Org. no. 935487579 Limited company (AS) Åmot Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 433,000
Operating profit NOK 40,000
Equity NOK 56,000
Incorporated 2025
Share capital NOK 525,000

SKOG OG MASKINDRIFT AS is registered as a limited company in Åmot, Innlandet with organisation number 935487579. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2025. Registered share capital is NOK 525,000, divided into 30000 shares. The company's stated purpose is: “Skog og landbruks tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 433,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2025

Revenue
NOK 433,000
Operating profit
NOK 40,000
Equity
NOK 56,000
Est. value
NOK 167,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SKOG OG MASKINDRIFT AS?

SKOG OG MASKINDRIFT AS
NOK 433,000 rev. · NOK 40,000 profit

SKOG OG MASKINDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKOG OG MASKINDRIFT AS

Who owns SKOG OG MASKINDRIFT AS?

Jøran Øylien Nyberget is the largest registered owner, with 90.0%.

What is the revenue of SKOG OG MASKINDRIFT AS?

SKOG OG MASKINDRIFT AS had revenue of NOK 433,000 in 2025.

Who is the general manager of SKOG OG MASKINDRIFT AS?

Jøran Øylien Nyberget is registered as general manager of SKOG OG MASKINDRIFT AS.

Where is SKOG OG MASKINDRIFT AS based?

SKOG OG MASKINDRIFT AS has its business address in Rena.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.