BIZTRAC BETA
Computer consultancy and computer facilities management activities

OSLO OMVENDT AS

Org. no. 931167472 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 72,000
Operating profit NOK 36,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

OSLO OMVENDT AS is registered as a limited company in Oslo, Oslo with organisation number 931167472. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilbyder av elektronisk musikkguide og promotering av arrangementer. Utviklertjenester for arrangører, promotører og andre interessenter for å skape egne IT-løsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 72,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 72,000
Operating profit
NOK 36,000
Equity
NOK 29,000
Est. value
NOK 132,000

Financial health · 2025

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

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

Who owns OSLO OMVENDT AS?

KALEIDOSKOP HOLDING AS
OSLO OMVENDT AS
NOK 72,000 rev. · NOK 36,000 profit

OSLO OMVENDT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO OMVENDT AS

Who owns OSLO OMVENDT AS?

KALEIDOSKOP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO OMVENDT AS?

OSLO OMVENDT AS had revenue of NOK 72,000 in 2025.

Where is OSLO OMVENDT AS based?

OSLO OMVENDT 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.