biztrac. BETA
COMPANY REGISTER PROFILE
899535162 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other support activities to arts and performing arts

OSLO INTERNASJONALE POESIFESTIVAL

Org. no. 899535162 Association/club/organisation (FLI) Oslo Incorporated 2005 Active
Revenue 2025 NOK 1.3m
Operating profit NOK −260,000
Equity NOK −331,000
Incorporated 2005

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−331k kr).

OSLO INTERNASJONALE POESIFESTIVAL is registered as a association/club/organisation in Oslo, Oslo with organisation number 899535162. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2005. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −260,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −31 %
Operating profit
NOK −260,000
▼ −456 %
Equity
NOK −331,000
▼ −363 %

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
-62.9%
Not satisfactory
Return on total assets
Solidity
-72.7%
Weak
Equity as a share of total capital

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

Who owns OSLO INTERNASJONALE POESIFESTIVAL?

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

Frequently asked questions about OSLO INTERNASJONALE POESIFESTIVAL

What is the revenue of OSLO INTERNASJONALE POESIFESTIVAL?

OSLO INTERNASJONALE POESIFESTIVAL had revenue of NOK 1.3m in 2025.

Who is the general manager of OSLO INTERNASJONALE POESIFESTIVAL?

Birgit Hatlehol is registered as general manager of OSLO INTERNASJONALE POESIFESTIVAL.

Where is OSLO INTERNASJONALE POESIFESTIVAL based?

OSLO INTERNASJONALE POESIFESTIVAL has its business address in Oslo.

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.