BIZTRAC BETA
COMPANY REGISTER PROFILE
922336806 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

APRIMO RÅDGIVNING ROGER ØQVIST AS

Org. no. 922336806 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 1.1m
Incorporated 2019
Share capital NOK 30,000

Signals

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

APRIMO RÅDGIVNING ROGER ØQVIST AS is registered as a limited company in Oslo, Oslo with organisation number 922336806. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivningsvirksomhet innenfor det økonomisk-/administrative området hovedsakelig til selskaper.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 1.1m
Est. value
NOK 728,000

Financial health · 2025

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

Who owns APRIMO RÅDGIVNING ROGER ØQVIST AS?

NILS BENGT ROGER ØQVIST
APRIMO RÅDGIVNING ROGER ØQVIST AS
· NOK −11,000 profit

APRIMO RÅDGIVNING ROGER ØQVIST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about APRIMO RÅDGIVNING ROGER ØQVIST AS

Who owns APRIMO RÅDGIVNING ROGER ØQVIST AS?

NILS BENGT ROGER ØQVIST is the largest registered owner, with 100.0%.

Who is the general manager of APRIMO RÅDGIVNING ROGER ØQVIST AS?

Nils Bengt Roger Øqvist is registered as general manager of APRIMO RÅDGIVNING ROGER ØQVIST AS.

Where is APRIMO RÅDGIVNING ROGER ØQVIST AS based?

APRIMO RÅDGIVNING ROGER ØQVIST AS has its business address in Oslo.

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.