biztrac. BETA
COMPANY REGISTER PROFILE
992138122 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

BERGEN INTERNASJONALE KULTURSENTER

Org. no. 992138122 Association/club/organisation (FLI) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 5.4m
Operating profit NOK 68,000
Equity NOK 409,000
Incorporated 2007
Employees 11

BERGEN INTERNASJONALE KULTURSENTER is registered as a association/club/organisation in Bergen, Vestland with organisation number 992138122. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2007 and has 11 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 5.4m in revenue and NOK 68,000 in operating profit.

Former names: FORENINGEN BERGEN INTERNASJONALE KULTURSENTER

Key figures · 2025

Revenue
NOK 5.4m
▼ −12 %
Operating profit
NOK 68,000
▲ +160 %
Equity
NOK 409,000
▲ +28 %
Est. value
NOK 876,000

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
11.7%
Good
Return on total assets
Solidity
44.7%
Very good
Equity as a share of total capital

Who owns BERGEN INTERNASJONALE KULTURSENTER?

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

Frequently asked questions about BERGEN INTERNASJONALE KULTURSENTER

What is the revenue of BERGEN INTERNASJONALE KULTURSENTER?

BERGEN INTERNASJONALE KULTURSENTER had revenue of NOK 5.4m in 2025.

Who is the general manager of BERGEN INTERNASJONALE KULTURSENTER?

Synnøve Eide is registered as general manager of BERGEN INTERNASJONALE KULTURSENTER.

Where is BERGEN INTERNASJONALE KULTURSENTER based?

BERGEN INTERNASJONALE KULTURSENTER has its business address in Bergen.

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.