BIZTRAC BETA
Publishing of books

CAMPUS GYMIR AS

Org. no. 936015727 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

CAMPUS GYMIR AS is registered as a limited company in Oslo, Oslo with organisation number 936015727. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og utgivelse av bøker, pamfletter, tidsskrifter, seminarer, foredrag og offentlige samtaler, drift av øvings- og samtalegrupper, redaksjonelt arbeid, musikalske komposisjoner og dertil sceniske arrangementer og fremføringer som fordrer en sunn aktivering av tilhørere/tilskuere.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 21,000
Est. value
NOK 38,000

Financial health · 2025

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

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

Who owns CAMPUS GYMIR AS?

OLE HARALD DAHL
CAMPUS GYMIR AS
NOK 0 rev. · NOK −3,000 profit

CAMPUS GYMIR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAMPUS GYMIR AS

Who owns CAMPUS GYMIR AS?

OLE HARALD DAHL is the largest registered owner, with 100.0%.

What is the revenue of CAMPUS GYMIR AS?

CAMPUS GYMIR AS had revenue of NOK 0 in 2025.

Where is CAMPUS GYMIR AS based?

CAMPUS GYMIR 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.