BIZTRAC BETA
Uoppgitt

ROGA AS

Org. no. 932561743 Limited company (AS) Inderøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK 5.0m
Incorporated 2023
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17k kr).

ROGA AS is registered as a limited company in Inderøy, Trøndelag with organisation number 932561743. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 35,000, divided into 1650 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 5.0m
Est. value
NOK 7.2m

Financial health · 2024

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

Who owns ROGA AS?

ROGER GAUSEN
ROGA AS
NOK 0 rev. · NOK −17,000 profit

ROGA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROGA AS own?

ROGA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROGA AS

Who owns ROGA AS?

ROGER GAUSEN is the largest registered owner, with 100.0%.

What is the revenue of ROGA AS?

ROGA AS had revenue of NOK 0 in 2024.

Who is the general manager of ROGA AS?

Roger Gausen is registered as general manager of ROGA AS.

Where is ROGA AS based?

ROGA AS has its business address in Inderøy.

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.