BIZTRAC BETA
Civil engineering activities

RGS DRIFT AS

Org. no. 817017142 Limited company (AS) Nes Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 519,000
Equity NOK 1.2m
Incorporated 2016
Employees 7
Share capital NOK 30,000

RGS DRIFT AS is registered as a limited company in Nes, Akershus with organisation number 817017142. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av konsulenttjenester innen bygg og anlegg, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 519,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 519,000
Equity
NOK 1.2m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns RGS DRIFT AS?

ODEGARD 1 HOLDING AS
RGS DRIFT AS
NOK 7.2m rev. · NOK 519,000 profit

RGS DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RGS DRIFT AS

Who owns RGS DRIFT AS?

ODEGARD 1 HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of RGS DRIFT AS?

RGS DRIFT AS had revenue of NOK 7.2m in 2024.

Who is the general manager of RGS DRIFT AS?

Geir Asle Ødegård is registered as general manager of RGS DRIFT AS.

Where is RGS DRIFT AS based?

RGS DRIFT AS has its business address in Rånåsfoss.

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.