BIZTRAC BETA
Site preparation

RØNNINGEN MASKIN AS

Org. no. 988132020 Limited company (AS) Nes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 68.7m
Operating profit NOK 693,000
Equity NOK 31.0m
Incorporated 2005
Employees 29
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-06-18 Aksjekapital registrert 2026-06-18.

RØNNINGEN MASKIN AS is registered as a limited company in Nes, Akershus with organisation number 988132020. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005 and has 29 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av entreprenørselskap med graving og transport. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 68.7m in revenue and NOK 693,000 in operating profit.

Key figures · 2024

Revenue
NOK 68.7m
Operating profit
NOK 693,000
Equity
NOK 31.0m
Est. value
NOK 15.9m

Financial health · 2024

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

Who owns RØNNINGEN MASKIN AS?

ERIK KRISTIAN RØNNINGEN
RØNNINGEN MASKIN AS
NOK 68.7m rev. · NOK 693,000 profit

RØNNINGEN MASKIN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØNNINGEN MASKIN AS

Who owns RØNNINGEN MASKIN AS?

ERIK KRISTIAN RØNNINGEN is the largest registered owner, with 25.0%.

What is the revenue of RØNNINGEN MASKIN AS?

RØNNINGEN MASKIN AS had revenue of NOK 68.7m in 2024.

Who is the general manager of RØNNINGEN MASKIN AS?

Håkon Rønningen is registered as general manager of RØNNINGEN MASKIN AS.

Where is RØNNINGEN MASKIN AS based?

RØNNINGEN MASKIN AS has its business address in Årnes.

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.