biztrac. BETA
COMPANY REGISTER PROFILE
927373912 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in dramatic arts

HALSEID KULTUR AS

Org. no. 927373912 Limited company (AS) Haugesund Incorporated 2021 Active
Revenue 2025 NOK 216,000
Operating profit NOK 16,000
Equity NOK 23,000
Incorporated 2021
Share capital NOK 30,000

HALSEID KULTUR AS is registered as a limited company in Haugesund, Rogaland with organisation number 927373912. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Opptreden, rådgiving, arrangement og kurs innen kultur og helse.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
▲ +5 %
Operating profit
NOK 16,000
▲ +207 %
Equity
NOK 23,000
▲ +114 %
Est. value
NOK 123,000

Financial health · 2025

Liquidity
2.13
Very good
Current assets ÷ current liabilities
Profitability
38.9%
Very good
Return on total assets
Solidity
43.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HALSEID KULTUR AS?

HALSEID KULTUR AS
NOK 216,000 rev. · NOK 16,000 profit

HALSEID KULTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALSEID KULTUR AS

Who owns HALSEID KULTUR AS?

Irene Halseid is the largest registered owner, with 100.0%.

What is the revenue of HALSEID KULTUR AS?

HALSEID KULTUR AS had revenue of NOK 216,000 in 2025.

Who is the general manager of HALSEID KULTUR AS?

Irene Halseid is registered as general manager of HALSEID KULTUR AS.

Where is HALSEID KULTUR AS based?

HALSEID KULTUR AS has its business address in Haugesund.

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.