BIZTRAC BETA
Sports and recreation education

JOBBSTREKKEN AS

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

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-28 Adresseendring registrert 2026-04-28.

JOBBSTREKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 924294639. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å tilby undervisning innen idrett og rekreasjon, eventarrangementer, samt annen tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 30,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns JOBBSTREKKEN AS?

KILDE AS
JOBBSTREKKEN AS
NOK 0 rev. · NOK −6,000 profit

JOBBSTREKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOBBSTREKKEN AS

Who owns JOBBSTREKKEN AS?

KILDE AS is the largest registered owner, with 100.0%.

What is the revenue of JOBBSTREKKEN AS?

JOBBSTREKKEN AS had revenue of NOK 0 in 2025.

Where is JOBBSTREKKEN AS based?

JOBBSTREKKEN 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.