BIZTRAC BETA
Activities of excursion and event organisers

YRKESBILSEMINARET.NO AS

Org. no. 928851389 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −20,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−20k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

YRKESBILSEMINARET.NO AS is registered as a limited company in Drammen, Buskerud with organisation number 928851389. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Arrangere Yrkesbilseminaret og alt som står i forbindelse med dette, samt ved kjøp av aksjer eller på annen måte delta i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −10,000
Equity
NOK −20,000

Financial health · 2025

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

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

Who owns YRKESBILSEMINARET.NO AS?

ZEVEN INVEST AS
YRKESBILSEMINARET.NO AS
· NOK −10,000 profit

YRKESBILSEMINARET.NO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about YRKESBILSEMINARET.NO AS

Who owns YRKESBILSEMINARET.NO AS?

ZEVEN INVEST AS is the largest registered owner, with 60.0%.

Who is the general manager of YRKESBILSEMINARET.NO AS?

Erik De Jager is registered as general manager of YRKESBILSEMINARET.NO AS.

Where is YRKESBILSEMINARET.NO AS based?

YRKESBILSEMINARET.NO AS has its business address in Drammen.

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.