BIZTRAC BETA
Removal services

VIKA FLYTTEBYRÅ OG MONTERING AS

Org. no. 923300678 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 9.3m
Operating profit NOK 83,000
Equity NOK 219,000
Incorporated 2019
Employees 28
Share capital NOK 30,000

VIKA FLYTTEBYRÅ OG MONTERING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 923300678. The business is classified under removal services (NACE 49.420). The company was incorporated in 2019 and has 28 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Flyttetjenester for private og bedrifter. Montering av møbler, rekvisita og annet relevant i forbindelse med flytting. Prosjektledelse og rådgivende tjenester for næring i samband med flytteprosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.3m in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.3m
Operating profit
NOK 83,000
Equity
NOK 219,000
Est. value
NOK 351,000

Financial health · 2025

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

Who owns VIKA FLYTTEBYRÅ OG MONTERING AS?

PAYTIM MULAKU
VIKA FLYTTEBYRÅ OG MONTERING AS
NOK 9.3m rev. · NOK 83,000 profit

VIKA FLYTTEBYRÅ OG MONTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKA FLYTTEBYRÅ OG MONTERING AS

Who owns VIKA FLYTTEBYRÅ OG MONTERING AS?

PAYTIM MULAKU is the largest registered owner, with 100.0%.

What is the revenue of VIKA FLYTTEBYRÅ OG MONTERING AS?

VIKA FLYTTEBYRÅ OG MONTERING AS had revenue of NOK 9.3m in 2025.

Where is VIKA FLYTTEBYRÅ OG MONTERING AS based?

VIKA FLYTTEBYRÅ OG MONTERING AS has its business address in Skedsmokorset.

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.