BIZTRAC BETA
COMPANY REGISTER PROFILE
942179626 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LANGE MASKIN AS

Org. no. 942179626 Limited company (AS) Molde Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 26,000
Operating profit NOK −130,000
Equity NOK −167,000
Incorporated 1986
Share capital NOK 892,000

Signals

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

LANGE MASKIN AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 942179626. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1986. Registered share capital is NOK 892,000, divided into 892 shares. The company's stated purpose is: “Drive handel, produksjon og annen økonomisk virksomhet, herunder å delta i norske og utenlandske selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK −130,000
Equity
NOK −167,000

Financial health · 2025

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-219.8%
Weak
Equity as a share of total capital

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

Who owns LANGE MASKIN AS?

ERIK LANGE FOLKE-OLSEN
LANGE MASKIN AS
NOK 26,000 rev. · NOK −130,000 profit

LANGE MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGE MASKIN AS

Who owns LANGE MASKIN AS?

ERIK LANGE FOLKE-OLSEN is the largest registered owner, with 100.0%.

What is the revenue of LANGE MASKIN AS?

LANGE MASKIN AS had revenue of NOK 26,000 in 2025.

Where is LANGE MASKIN AS based?

LANGE MASKIN AS has its business address in Molde.

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.