biztrac. BETA
COMPANY REGISTER PROFILE
935841038 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

FORESTNORD ANLEGG AS

Org. no. 935841038 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 382,000
Operating profit NOK −11,000
Equity NOK 11,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

FORESTNORD ANLEGG AS is registered as a limited company in Bærum, Akershus with organisation number 935841038. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Transport av skogsmaskiner, anleggsmaskiner og annet som står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 382,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 382,000
▼ −58 %
Operating profit
NOK −11,000
▼ −102 %
Equity
NOK 11,000
▼ −97 %
Est. value
NOK 184,000

Financial health · 2025

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

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

Who owns FORESTNORD ANLEGG AS?

FORESTNORD ANLEGG AS
NOK 382,000 rev. · NOK −11,000 profit

FORESTNORD ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FORESTNORD ANLEGG AS

Who owns FORESTNORD ANLEGG AS?

Simen Waal Fjeldet is the largest registered owner, with 50.0%.

What is the revenue of FORESTNORD ANLEGG AS?

FORESTNORD ANLEGG AS had revenue of NOK 382,000 in 2025.

Where is FORESTNORD ANLEGG AS based?

FORESTNORD ANLEGG AS has its business address in Kolsås.

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.