BIZTRAC BETA
Other specialised construction activities n.e.c.

RG FJELLSIKRING AS

Org. no. 924823755 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 19.6m
Operating profit NOK 3.2m
Equity NOK 126,000
Incorporated 2020
Employees 18
Share capital NOK 30,000

RG FJELLSIKRING AS is registered as a limited company in Larvik, Vestfold with organisation number 924823755. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2020 and has 18 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fjellsikring, borring med rigg, sikring av fjell. Konsulentvirksomhet innenfor fjellsikring, sikring av bygg og anlegg. Opplæring av boreriggoperatører.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.6m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 19.6m
Operating profit
NOK 3.2m
Equity
NOK 126,000
Est. value
NOK 8.7m

Financial health · 2024

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

Who owns RG FJELLSIKRING AS?

RHG HOLDING AS
RG FJELLSIKRING AS
NOK 19.6m rev. · NOK 3.2m profit

RG FJELLSIKRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RG FJELLSIKRING AS

Who owns RG FJELLSIKRING AS?

RHG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RG FJELLSIKRING AS?

RG FJELLSIKRING AS had revenue of NOK 19.6m in 2024.

Who is the general manager of RG FJELLSIKRING AS?

Roger Hellenes Granerud is registered as general manager of RG FJELLSIKRING AS.

Where is RG FJELLSIKRING AS based?

RG FJELLSIKRING AS has its business address in Larvik.

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.