BIZTRAC BETA
Rental and leasing of recreational and sports goods

MILE MOBILITY AS

Org. no. 927064812 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.1m
Equity NOK −181,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−181k kr).

MILE MOBILITY AS is registered as a limited company in Lillehammer, Innlandet with organisation number 927064812. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av elektriske sparkesykler via app.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.1m
Equity
NOK −181,000
Est. value
NOK 5.3m

Financial health · 2024

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

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

Who owns MILE MOBILITY AS?

KURSLEVERANDØREN AS
MILE MOBILITY AS
NOK 3.1m rev. · NOK 1.1m profit

MILE MOBILITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILE MOBILITY AS

Who owns MILE MOBILITY AS?

KURSLEVERANDØREN AS is the largest registered owner, with 100.0%.

What is the revenue of MILE MOBILITY AS?

MILE MOBILITY AS had revenue of NOK 3.1m in 2024.

Who is the general manager of MILE MOBILITY AS?

Ivar Andreas Zervas is registered as general manager of MILE MOBILITY AS.

Where is MILE MOBILITY AS based?

MILE MOBILITY AS has its business address in Lillehammer.

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.