biztrac. BETA
COMPANY REGISTER PROFILE
971490896 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Activities of religious organisations

CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY

Org. no. 971490896 Association/club/organisation (FLI) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 11.4m
Operating profit NOK 2.6m
Equity NOK 35.4m
Incorporated 1989
Employees 13

CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY is registered as a association/club/organisation in Oslo, Oslo with organisation number 971490896. The business is classified under activities of religious organisations (NACE 94.910). The company was incorporated in 1989 and has 13 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 11.4m in revenue and NOK 2.6m in operating profit.

Former names: WORLD ISLAMIC MISSION NORWAY -, WORLD ISLAMIC MISSION NORWAY, FIRST CENTRAL JAM E MOSQUE

Key figures · 2025

Revenue
NOK 11.4m
▲ +1 %
Operating profit
NOK 2.6m
▼ −25 %
Equity
NOK 35.4m
▲ +7 %
Est. value
NOK 28.6m

Financial health · 2025

Liquidity
11.64
Very good
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
93.4%
Very good
Equity as a share of total capital

Who owns CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY?

No shareholders are registered for CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY

What is the revenue of CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY?

CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY had revenue of NOK 11.4m in 2025.

Where is CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY based?

CENTRAL JAM-E-MOSQUE WORLD ISLAMIC MISSION NORWAY has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.