BIZTRAC BETA
Other technical consultancy

JOTNE MOBILITY AS

Org. no. 993382515 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 29.4m
Operating profit NOK 1.1m
Equity NOK 2.4m
Incorporated 2008
Share capital NOK 2.0m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

JOTNE MOBILITY AS is registered as a limited company in Bærum, Akershus with organisation number 993382515. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2008. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Rådgivning, konstruksjon, utvikling og leveranse av utstyr innen rullende materiell samt hva som står i forbindelse med dette. Selskapet kan også eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 29.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 29.4m
Operating profit
NOK 1.1m
Equity
NOK 2.4m
Est. value
NOK 6.7m

Financial health · 2024

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns JOTNE MOBILITY AS?

JOTNE INDUSTRIER AS
JOTNE MOBILITY AS
NOK 29.4m rev. · NOK 1.1m profit

JOTNE MOBILITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOTNE MOBILITY AS

Who owns JOTNE MOBILITY AS?

JOTNE INDUSTRIER AS is the largest registered owner, with 100.0%.

What is the revenue of JOTNE MOBILITY AS?

JOTNE MOBILITY AS had revenue of NOK 29.4m in 2024.

Where is JOTNE MOBILITY AS based?

JOTNE MOBILITY AS has its business address in Fornebu.

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.