BIZTRAC BETA
Other support activities to arts and performing arts

COFFEEBREAK AGENCY AS

Org. no. 931997165 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 251,000
Equity NOK 317,000
Incorporated 2023
Share capital NOK 40,000

COFFEEBREAK AGENCY AS is registered as a limited company in Oslo, Oslo with organisation number 931997165. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Selge varer og tjenester innen scenetjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 251,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 251,000
Equity
NOK 317,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns COFFEEBREAK AGENCY AS?

KIM RUNE HAGEN
COFFEEBREAK AGENCY AS
NOK 1.9m rev. · NOK 251,000 profit

COFFEEBREAK AGENCY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about COFFEEBREAK AGENCY AS

Who owns COFFEEBREAK AGENCY AS?

KIM RUNE HAGEN is the largest registered owner, with 50.0%.

What is the revenue of COFFEEBREAK AGENCY AS?

COFFEEBREAK AGENCY AS had revenue of NOK 1.9m in 2024.

Who is the general manager of COFFEEBREAK AGENCY AS?

Kim Rune Hagen is registered as general manager of COFFEEBREAK AGENCY AS.

Where is COFFEEBREAK AGENCY AS based?

COFFEEBREAK AGENCY AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

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