biztrac. BETA
COMPANY REGISTER PROFILE
933219283 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

DRIVEN BY JL AS

Org. no. 933219283 Limited company (AS) Tjeldsund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −27,000
Equity NOK 1.1m
Incorporated 2024
Share capital NOK 60,000

Signals

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

DRIVEN BY JL AS is registered as a limited company in Tjeldsund, Troms with organisation number 933219283. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer i andre selskap samt virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −27,000
▼ −30 %
Equity
NOK 1.1m
▼ −0 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
4.0%
Weak
Return on total assets
Solidity
18.3%
Good
Equity as a share of total capital

Who owns DRIVEN BY JL AS?

DRIVEN BY JL AS
NOK 0 rev. · NOK −27,000 profit

DRIVEN BY JL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DRIVEN BY JL AS own?

DRIVEN BY JL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DRIVEN BY JL AS

Who owns DRIVEN BY JL AS?

Jonas Mork Lunde is the largest registered owner, with 100.0%.

What is the revenue of DRIVEN BY JL AS?

DRIVEN BY JL AS had revenue of NOK 0 in 2025.

Where is DRIVEN BY JL AS based?

DRIVEN BY JL AS has its business address in Evenskjer.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.