biztrac. BETA
COMPANY REGISTER PROFILE
936185487 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Water collection, treatment and supply

FINNSKOGEN PRODUKSJON AS

Org. no. 936185487 Limited company (AS) Grue Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −243,000
Equity NOK −177,000
Incorporated 2025
Share capital NOK 80,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−177k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−243k kr).

FINNSKOGEN PRODUKSJON AS is registered as a limited company in Grue, Innlandet with organisation number 936185487. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2025. Registered share capital is NOK 80,000, divided into 800000 shares. The company's stated purpose is: “Bearbeiding og utvinning av natur og vannressurser, samt alt som herved står i forbindelse med dette, herunder deltakelse i andre selskaper med samme eller lignende formål.”.

Key figures · 2025

Operating profit
NOK −243,000
Equity
NOK −177,000

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-33.1%
Weak
Equity as a share of total capital

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

Who owns FINNSKOGEN PRODUKSJON AS?

FINNSKOGEN PRODUKSJON AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINNSKOGEN PRODUKSJON AS

Who owns FINNSKOGEN PRODUKSJON AS?

Jan Erik Finne is the largest registered owner, with 38.8%.

Who is the general manager of FINNSKOGEN PRODUKSJON AS?

Ole Albert Eig is registered as general manager of FINNSKOGEN PRODUKSJON AS.

Where is FINNSKOGEN PRODUKSJON AS based?

FINNSKOGEN PRODUKSJON AS has its business address in Grue Finnskog.

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.