biztrac. BETA
COMPANY REGISTER PROFILE
815554922 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Visual arts creation activities

KULTUR-KAMERATENE AS

Org. no. 815554922 Limited company (AS) Kragerø Incorporated 2015 Active
Revenue 2025 NOK 310,000
Operating profit NOK 37,000
Equity NOK 16,000
Incorporated 2015
Share capital NOK 30,000

KULTUR-KAMERATENE AS is registered as a limited company in Kragerø, Telemark with organisation number 815554922. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kunst og kulturutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 310,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 310,000
▼ −0 %
Operating profit
NOK 37,000
▲ +403 %
Equity
NOK 16,000
▲ +178 %
Est. value
NOK 140,000

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
16.7%
Weak
Equity as a share of total capital

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

Who owns KULTUR-KAMERATENE AS?

KULTUR-KAMERATENE AS
NOK 310,000 rev. · NOK 37,000 profit

KULTUR-KAMERATENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KULTUR-KAMERATENE AS

Who owns KULTUR-KAMERATENE AS?

Katja C Ræder Aarflot is the largest registered owner, with 100.0%.

What is the revenue of KULTUR-KAMERATENE AS?

KULTUR-KAMERATENE AS had revenue of NOK 310,000 in 2025.

Who is the general manager of KULTUR-KAMERATENE AS?

Katja C Ræder Aarflot is registered as general manager of KULTUR-KAMERATENE AS.

Where is KULTUR-KAMERATENE AS based?

KULTUR-KAMERATENE AS has its business address in Kragerø.

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.