BIZTRAC BETA
Wholesale of other machinery and equipment

RUNTIME ENGINEERING AS

Org. no. 932166135 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK −741,000
Equity NOK −902,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

RUNTIME ENGINEERING AS is registered as a limited company in Oslo, Oslo with organisation number 932166135. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av vifter og reservedeler til vifter, service og reparasjon og forebyggende vedlikehold”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK −741,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK −741,000
Equity
NOK −902,000

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-24.8%
Weak
Equity as a share of total capital

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

Who owns RUNTIME ENGINEERING AS?

ERINOVA GROUP AB
RUNTIME ENGINEERING AS
NOK 4.8m rev. · NOK −741,000 profit

RUNTIME ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUNTIME ENGINEERING AS

Who owns RUNTIME ENGINEERING AS?

ERINOVA GROUP AB is the largest registered owner, with 100.0%.

What is the revenue of RUNTIME ENGINEERING AS?

RUNTIME ENGINEERING AS had revenue of NOK 4.8m in 2025.

Where is RUNTIME ENGINEERING AS based?

RUNTIME ENGINEERING AS has its business address in Oslo.

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.