BIZTRAC BETA
Removal services

FLYTTETRANS AS

Org. no. 930324531 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK −24,000
Equity NOK −95,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−95k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).

FLYTTETRANS AS is registered as a limited company in Oslo, Oslo with organisation number 930324531. The business is classified under removal services (NACE 49.420). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive med hurtig flytting og transport og tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK −24,000
Equity
NOK −95,000

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.5%
Weak
Equity as a share of total capital

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

Who owns FLYTTETRANS AS?

Bahri Isufi
FLYTTETRANS AS
NOK 3.3m rev. · NOK −24,000 profit

FLYTTETRANS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLYTTETRANS AS

Who owns FLYTTETRANS AS?

Bahri Isufi is the largest registered owner, with 50.0%.

What is the revenue of FLYTTETRANS AS?

FLYTTETRANS AS had revenue of NOK 3.3m in 2025.

Who is the general manager of FLYTTETRANS AS?

Bahri Isufi is registered as general manager of FLYTTETRANS AS.

Where is FLYTTETRANS AS based?

FLYTTETRANS 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.