BIZTRAC BETA
Activities of insurance agents and brokers

GIMNES FORSIKRINGSPARTNER AS

Org. no. 917213755 Limited company (AS) Hustadvika Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 439,000
Equity NOK 167,000
Incorporated 2016
Share capital NOK 30,000

GIMNES FORSIKRINGSPARTNER AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 917213755. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Salg og formidling av forsikring, agenturvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 439,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 439,000
Equity
NOK 167,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns GIMNES FORSIKRINGSPARTNER AS?

GIMNES INVEST AS
GIMNES FORSIKRINGSPARTNER AS
NOK 2.0m rev. · NOK 439,000 profit

GIMNES FORSIKRINGSPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIMNES FORSIKRINGSPARTNER AS

Who owns GIMNES FORSIKRINGSPARTNER AS?

GIMNES INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GIMNES FORSIKRINGSPARTNER AS?

GIMNES FORSIKRINGSPARTNER AS had revenue of NOK 2.0m in 2025.

Who is the general manager of GIMNES FORSIKRINGSPARTNER AS?

Frode Gimnes is registered as general manager of GIMNES FORSIKRINGSPARTNER AS.

Where is GIMNES FORSIKRINGSPARTNER AS based?

GIMNES FORSIKRINGSPARTNER AS has its business address in Eide.

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.