BIZTRAC BETA
COMPANY REGISTER PROFILE
975940608 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Activities of religious organisations

THE ANGLICAN CHAPLAINCY IN NORWAY

Org. no. 975940608 Association/club/organisation (FLI) Oslo Incorporated 1881 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK −517,000
Equity NOK 7.3m
Incorporated 1881
Employees 6

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−517k kr).

THE ANGLICAN CHAPLAINCY IN NORWAY is registered as a association/club/organisation in Oslo, Oslo with organisation number 975940608. The business is classified under activities of religious organisations (NACE 94.910). The company was incorporated in 1881 and has 6 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK −517,000 in operating profit.

Former names: SAINT EDMUND'S CHURCH, OSLO

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK −517,000
Equity
NOK 7.3m
Est. value
NOK 6.1m

Financial health · 2024

Liquidity
12.05
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
93.0%
Very good
Equity as a share of total capital

Who owns THE ANGLICAN CHAPLAINCY IN NORWAY?

No shareholders are registered for THE ANGLICAN CHAPLAINCY IN NORWAY in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about THE ANGLICAN CHAPLAINCY IN NORWAY

What is the revenue of THE ANGLICAN CHAPLAINCY IN NORWAY?

THE ANGLICAN CHAPLAINCY IN NORWAY had revenue of NOK 3.4m in 2025.

Who is the general manager of THE ANGLICAN CHAPLAINCY IN NORWAY?

Ingeborg Wörheide is registered as general manager of THE ANGLICAN CHAPLAINCY IN NORWAY.

Where is THE ANGLICAN CHAPLAINCY IN NORWAY based?

THE ANGLICAN CHAPLAINCY IN 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 02.09.2026.

Report a problem

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