BIZTRAC BETA
Activities of insurance agents and brokers

IAM INSURANCE AS

Org. no. 916914059 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 15.5m
Operating profit NOK 150,000
Equity NOK 554,000
Incorporated 2016
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

IAM INSURANCE AS is registered as a limited company in Oslo, Oslo with organisation number 916914059. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Opptre som agentvirksomhet innen garantiforsikring.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.5m in revenue and NOK 150,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.5m
Operating profit
NOK 150,000
Equity
NOK 554,000
Est. value
NOK 843,000

Financial health · 2024

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

Who owns IAM INSURANCE AS?

INSURANCE HOLDING AS
IAM INSURANCE AS
NOK 15.5m rev. · NOK 150,000 profit

IAM INSURANCE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IAM INSURANCE AS

Who owns IAM INSURANCE AS?

INSURANCE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of IAM INSURANCE AS?

IAM INSURANCE AS had revenue of NOK 15.5m in 2024.

Who is the general manager of IAM INSURANCE AS?

John Killengreen is registered as general manager of IAM INSURANCE AS.

Where is IAM INSURANCE AS based?

IAM INSURANCE AS has its business address in Oslo.

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.