BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

RALLAB AS

Org. no. 936596118 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 72,000
Operating profit NOK 14,000
Equity NOK 41,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-15.

RALLAB AS is registered as a limited company in Lillestrøm, Akershus with organisation number 936596118. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Slange- og koblingsforetak, som jobber med applikasjoner innen industri, slamsuging, pumper, tørrsug, brønnboring, maskinutleie, renseverk/sandblåsing, ADR/tankbil og raffineri, bulktransport/næringsm.”. The most recent filed accounts, for the 2025 financial year, show NOK 72,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 72,000
Operating profit
NOK 14,000
Equity
NOK 41,000
Est. value
NOK 61,000

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.8%
Weak
Equity as a share of total capital

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

Who owns RALLAB AS?

INDUSTRISPECIALISTEN RALLAB AB
RALLAB AS
NOK 72,000 rev. · NOK 14,000 profit

RALLAB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RALLAB AS

Who owns RALLAB AS?

INDUSTRISPECIALISTEN RALLAB AB is the largest registered owner, with 100.0%.

What is the revenue of RALLAB AS?

RALLAB AS had revenue of NOK 72,000 in 2025.

Where is RALLAB AS based?

RALLAB AS has its business address in Lillestrøm.

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.