BIZTRAC BETA
Removal services

STAVANGER FLYTTEBYRÅ AS

Org. no. 915559603 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 123,000
Equity NOK 282,000
Incorporated 2015
Share capital NOK 30,000

STAVANGER FLYTTEBYRÅ AS is registered as a limited company in Stavanger, Rogaland with organisation number 915559603. The business is classified under removal services (NACE 49.420). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Flytte-, transport, - og lagertjenester og annet som naturlig faller sammen med dette, herunder å ha eierinteresser i andre foretak med liknende eller forretningsmessig tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 123,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 123,000
Equity
NOK 282,000
Est. value
NOK 463,000

Financial health · 2025

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

Who owns STAVANGER FLYTTEBYRÅ AS?

IMTANAN AHMAD MALIK
STAVANGER FLYTTEBYRÅ AS
NOK 4.5m rev. · NOK 123,000 profit

STAVANGER FLYTTEBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER FLYTTEBYRÅ AS

Who owns STAVANGER FLYTTEBYRÅ AS?

IMTANAN AHMAD MALIK is the largest registered owner, with 100.0%.

What is the revenue of STAVANGER FLYTTEBYRÅ AS?

STAVANGER FLYTTEBYRÅ AS had revenue of NOK 4.5m in 2025.

Who is the general manager of STAVANGER FLYTTEBYRÅ AS?

Imtanan Ahmad Malik is registered as general manager of STAVANGER FLYTTEBYRÅ AS.

Where is STAVANGER FLYTTEBYRÅ AS based?

STAVANGER FLYTTEBYRÅ AS has its business address in Stavanger.

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.