BIZTRAC BETA
Activities of insurance agents and brokers

MIDTNORSK FORSIKRING AS

Org. no. 998328012 Limited company (AS) Ørland Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 419,000
Equity NOK 60,000
Incorporated 2012
Share capital NOK 60,000

MIDTNORSK FORSIKRING AS is registered as a limited company in Ørland, Trøndelag with organisation number 998328012. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2012. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Konsulenter for salg av forsikring, leasing, fonds og annet som faller inn under finans.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 419,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 419,000
Equity
NOK 60,000
Est. value
NOK 1.2m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MIDTNORSK FORSIKRING AS?

ODD INGE HOVD
MIDTNORSK FORSIKRING AS
NOK 2.3m rev. · NOK 419,000 profit

MIDTNORSK FORSIKRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTNORSK FORSIKRING AS

Who owns MIDTNORSK FORSIKRING AS?

ODD INGE HOVD is the largest registered owner, with 100.0%.

What is the revenue of MIDTNORSK FORSIKRING AS?

MIDTNORSK FORSIKRING AS had revenue of NOK 2.3m in 2025.

Who is the general manager of MIDTNORSK FORSIKRING AS?

Odd Inge Hovd is registered as general manager of MIDTNORSK FORSIKRING AS.

Where is MIDTNORSK FORSIKRING AS based?

MIDTNORSK FORSIKRING AS has its business address in Bjugn.

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.