BIZTRAC BETA
Business and other management consultancy activities

FLEX MOBILITY AS

Org. no. 932199858 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 891
Equity NOK 31,000
Incorporated 2023
Share capital NOK 30,000

FLEX MOBILITY AS is registered as a limited company in Drammen, Buskerud with organisation number 932199858. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 891 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 891
Equity
NOK 31,000
Est. value
NOK 21,000

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Weak
Equity as a share of total capital

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

Who owns FLEX MOBILITY AS?

TOMAS HOEL
FLEX MOBILITY AS
NOK 2.2m rev. · NOK 891 profit

FLEX MOBILITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLEX MOBILITY AS

Who owns FLEX MOBILITY AS?

TOMAS HOEL is the largest registered owner, with 100.0%.

What is the revenue of FLEX MOBILITY AS?

FLEX MOBILITY AS had revenue of NOK 2.2m in 2024.

Who is the general manager of FLEX MOBILITY AS?

Tomas Hoel is registered as general manager of FLEX MOBILITY AS.

Where is FLEX MOBILITY AS based?

FLEX MOBILITY 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.