biztrac. BETA
COMPANY REGISTER PROFILE
836016572 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

RRN GROUP AS

Org. no. 836016572 Limited company (AS) Grimstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

RRN GROUP AS is registered as a limited company in Grimstad, Agder with organisation number 836016572. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 38,000

Financial health · 2025

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

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

Who owns RRN GROUP AS?

RRN GROUP AS
NOK 0 rev. · NOK 0 profit

RRN GROUP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RRN GROUP AS

Who owns RRN GROUP AS?

Eirik Holen is the largest registered owner, with 50.0%.

What is the revenue of RRN GROUP AS?

RRN GROUP AS had revenue of NOK 0 in 2025.

Who is the general manager of RRN GROUP AS?

Eirik Holen is registered as general manager of RRN GROUP AS.

Where is RRN GROUP AS based?

RRN GROUP AS has its business address in Fevik.

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.