BIZTRAC BETA
COMPANY REGISTER PROFILE
982797063 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Combined facilities support activities

BCC HAMAR

Org. no. 982797063 Association/club/organisation (FLI) Hamar Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 9.0m
Operating profit NOK 1.3m
Equity NOK 25.2m
Incorporated 1999

BCC HAMAR is registered as a association/club/organisation in Hamar, Innlandet with organisation number 982797063. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 1999. The most recent filed accounts, for the 2024 financial year, show NOK 9.0m in revenue and NOK 1.3m in operating profit.

Former names: DEN KRISTELIGE MENIGHET I HAMAR OG OMEGN, BRUNSTAD KRISTELIGE MENIGHET HAMAR

Key figures · 2024

Revenue
NOK 9.0m
Operating profit
NOK 1.3m
Equity
NOK 25.2m
Est. value
NOK 16.8m

Financial health · 2024

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

Who owns BCC HAMAR?

No shareholders are registered for BCC HAMAR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BCC HAMAR

What is the revenue of BCC HAMAR?

BCC HAMAR had revenue of NOK 9.0m in 2024.

Where is BCC HAMAR based?

BCC HAMAR has its business address in Ridabu.

Property

Business address Kurudvegen 94, 2322 Ridabu
Cadastral unit 3403-183/28/0/0
Building Bedehus, menighetshus · 2 units

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.