BIZTRAC BETA
Removal services

MJØSA FLYTTEBYRÅ AS

Org. no. 920677177 Limited company (AS) Hamar Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 467,000
Equity NOK 2.0m
Incorporated 2018
Employees 12
Share capital NOK 50,000

MJØSA FLYTTEBYRÅ AS is registered as a limited company in Hamar, Innlandet with organisation number 920677177. The business is classified under removal services (NACE 49.420). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Flytting, vasking, rydding, mellomlagring av innbo/eiendeler. Kjøp, salg og utleie av driftsmidler. Vaktmestertjenester, tømming av avfall. Kjøp, salg, rehabilitering og utleie av fast eiendom, Deltakelse i andre selskaper. Agenturvirksomhet, Investeringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 467,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 467,000
Equity
NOK 2.0m
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.0%
Very good
Equity as a share of total capital

Who owns MJØSA FLYTTEBYRÅ AS?

KRISTIAN GJØRA
MJØSA FLYTTEBYRÅ AS
NOK 7.2m rev. · NOK 467,000 profit

MJØSA FLYTTEBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MJØSA FLYTTEBYRÅ AS

Who owns MJØSA FLYTTEBYRÅ AS?

KRISTIAN GJØRA is the largest registered owner, with 100.0%.

What is the revenue of MJØSA FLYTTEBYRÅ AS?

MJØSA FLYTTEBYRÅ AS had revenue of NOK 7.2m in 2024.

Where is MJØSA FLYTTEBYRÅ AS based?

MJØSA FLYTTEBYRÅ AS has its business address in Hamar.

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.