BIZTRAC BETA
COMPANY REGISTER PROFILE
924058293 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

ROGJ INVEST AS

Org. no. 924058293 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 17,000
Incorporated 2019
Share capital NOK 36,000

Signals

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

ROGJ INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 924058293. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 36,000, divided into 300 shares. The company's stated purpose is: “Å eie og forvalte aksjer og investeringer, samt det som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Former names: G REGNSKAP AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
▲ +38 %
Equity
NOK 17,000
▼ −39 %
Est. value
NOK 20,000

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
26.8%
Very good
Return on total assets
Solidity
36.6%
Weak
Equity as a share of total capital

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

Who owns ROGJ INVEST AS?

ROGJ INVEST AS
NOK 0 rev. · NOK −11,000 profit

ROGJ INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROGJ INVEST AS

Who owns ROGJ INVEST AS?

RONNY GJØRØY is the largest registered owner, with 100.0%.

What is the revenue of ROGJ INVEST AS?

ROGJ INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of ROGJ INVEST AS?

Ronny Gjørøy is registered as general manager of ROGJ INVEST AS.

Where is ROGJ INVEST AS based?

ROGJ INVEST AS has its business address in Ulset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.