BIZTRAC BETA
Computer consultancy and computer facilities management activities

ORIC CONSULTING AS

Org. no. 925572667 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 82,000
Equity NOK 878,000
Incorporated 2020
Share capital NOK 30,000

ORIC CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 925572667. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen IT.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 82,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 82,000
Equity
NOK 878,000
Est. value
NOK 962,000

Financial health · 2024

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

Who owns ORIC CONSULTING AS?

ARNE VEGARD KÅSA
ORIC CONSULTING AS
NOK 2.6m rev. · NOK 82,000 profit

ORIC CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORIC CONSULTING AS own?

ORIC CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORIC CONSULTING AS

Who owns ORIC CONSULTING AS?

ARNE VEGARD KÅSA is the largest registered owner, with 100.0%.

What is the revenue of ORIC CONSULTING AS?

ORIC CONSULTING AS had revenue of NOK 2.6m in 2024.

Who is the general manager of ORIC CONSULTING AS?

Arne Vegard Kåsa is registered as general manager of ORIC CONSULTING AS.

Where is ORIC CONSULTING AS based?

ORIC CONSULTING 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.