BIZTRAC BETA
Activities of insurance agents and brokers

MJØSA FORSIKRING AS

Org. no. 927509849 Limited company (AS) Gjøvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 246,000
Equity NOK 993,000
Incorporated 2021
Employees 14
Share capital NOK 30,000

MJØSA FORSIKRING AS is registered as a limited company in Gjøvik, Innlandet with organisation number 927509849. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2021 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av forsikring, livsforsikring og finansielle tjenester, i tillegg kjøp og salg av aksjer og eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 246,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 246,000
Equity
NOK 993,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.7%
Very good
Equity as a share of total capital

Who owns MJØSA FORSIKRING AS?

FRANK ANDÅS
MJØSA FORSIKRING AS
NOK 3.9m rev. · NOK 246,000 profit

MJØSA FORSIKRING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MJØSA FORSIKRING AS own?

MJØSA FORSIKRING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MJØSA FORSIKRING AS

Who owns MJØSA FORSIKRING AS?

FRANK ANDÅS is the largest registered owner, with 100.0%.

What is the revenue of MJØSA FORSIKRING AS?

MJØSA FORSIKRING AS had revenue of NOK 3.9m in 2024.

Where is MJØSA FORSIKRING AS based?

MJØSA FORSIKRING AS has its business address in Gjøvik.

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.