biztrac. BETA
COMPANY REGISTER PROFILE
991854169 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Manufacture of ready-mixed concrete

RIL-BETONG AS

Org. no. 991854169 Limited company (AS) Øystre Slidre Incorporated 2007 Active
Revenue 2025 NOK 233,000
Operating profit NOK −663,000
Equity NOK 9.4m
Incorporated 2007
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−663k kr).

RIL-BETONG AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 991854169. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Produksjon og salg av grusmasser, betong mv samt transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 233,000 in revenue and NOK −663,000 in operating profit.

Key figures · 2025

Revenue
NOK 233,000
▼ −3 %
Operating profit
NOK −663,000
▲ +39 %
Equity
NOK 9.4m
▼ −11 %
Est. value
NOK 5.1m

Financial health · 2025

Liquidity
40.96
Very good
Current assets ÷ current liabilities
Profitability
-1.9%
Not satisfactory
Return on total assets
Solidity
98.1%
Very good
Equity as a share of total capital

Who owns RIL-BETONG AS?

RIL-BETONG AS
NOK 233,000 rev. · NOK −663,000 profit

RIL-BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIL-BETONG AS

Who owns RIL-BETONG AS?

Rolf Ivar Lykken is the largest registered owner, with 100.0%.

What is the revenue of RIL-BETONG AS?

RIL-BETONG AS had revenue of NOK 233,000 in 2025.

Who is the general manager of RIL-BETONG AS?

Rolf Ivar Lykken is registered as general manager of RIL-BETONG AS.

Where is RIL-BETONG AS based?

RIL-BETONG AS has its business address in Beitostølen.

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.