BIZTRAC BETA
Freight transport by road

FLYTTE TJENESTE AS

Org. no. 919220163 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 51,000
Equity NOK 262,000
Incorporated 2017
Employees 9
Share capital NOK 30,000

FLYTTE TJENESTE AS is registered as a limited company in Oslo, Oslo with organisation number 919220163. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Godstransport på vei, budtjenester, transport av varer og gods. Logistikk og herunder å kunne delta i selskap med lignende virksomhet, samt kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 51,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 51,000
Equity
NOK 262,000
Est. value
NOK 267,000

Financial health · 2024

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

Who owns FLYTTE TJENESTE AS?

AHMED DZHASEM MOHAMED
FLYTTE TJENESTE AS
NOK 2.0m rev. · NOK 51,000 profit

FLYTTE TJENESTE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLYTTE TJENESTE AS

Who owns FLYTTE TJENESTE AS?

AHMED DZHASEM MOHAMED is the largest registered owner, with 100.0%.

What is the revenue of FLYTTE TJENESTE AS?

FLYTTE TJENESTE AS had revenue of NOK 2.0m in 2024.

Who is the general manager of FLYTTE TJENESTE AS?

Ahmed Dzhasem Mohamed is registered as general manager of FLYTTE TJENESTE AS.

Where is FLYTTE TJENESTE AS based?

FLYTTE TJENESTE 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.