BIZTRAC BETA
Activities of insurance agents and brokers

OSLO FORSIKRINGSSENTER AS

Org. no. 892920052 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 20.9m
Operating profit NOK 1.4m
Equity NOK 100,000
Incorporated 2008
Employees 13
Share capital NOK 100,000

OSLO FORSIKRINGSSENTER AS is registered as a limited company in Oslo, Oslo with organisation number 892920052. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2008 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av forsikringer og det som naturlig hører inn under det.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 20.9m
Operating profit
NOK 1.4m
Equity
NOK 100,000
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns OSLO FORSIKRINGSSENTER AS?

CHRISTIAN NYQUIST-MELBØE
OSLO FORSIKRINGSSENTER AS
NOK 20.9m rev. · NOK 1.4m profit

OSLO FORSIKRINGSSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO FORSIKRINGSSENTER AS

Who owns OSLO FORSIKRINGSSENTER AS?

CHRISTIAN NYQUIST-MELBØE is the largest registered owner, with 100.0%.

What is the revenue of OSLO FORSIKRINGSSENTER AS?

OSLO FORSIKRINGSSENTER AS had revenue of NOK 20.9m in 2025.

Who is the general manager of OSLO FORSIKRINGSSENTER AS?

Christian Nyquist-Melbøe is registered as general manager of OSLO FORSIKRINGSSENTER AS.

Where is OSLO FORSIKRINGSSENTER AS based?

OSLO FORSIKRINGSSENTER 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.