BIZTRAC BETA
Beauty care and other beauty treatment activities

POETIKA AS

Org. no. 914866405 Limited company (AS) Stange Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 165,000
Equity NOK −143,000
Incorporated 2015
Employees 8
Share capital NOK 30,000

Signals

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

POETIKA AS is registered as a limited company in Stange, Innlandet with organisation number 914866405. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2015 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kosmetisk og estetisk-medisinsk behandling, sertifisering, kurs og opplæring, samt salg av kosmetikk og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 165,000
Equity
NOK −143,000
Est. value
NOK 951,000

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.4%
Weak
Equity as a share of total capital

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

Who owns POETIKA AS?

IRINA ERVIK
POETIKA AS
NOK 4.1m rev. · NOK 165,000 profit

POETIKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POETIKA AS

Who owns POETIKA AS?

IRINA ERVIK is the largest registered owner, with 100.0%.

What is the revenue of POETIKA AS?

POETIKA AS had revenue of NOK 4.1m in 2024.

Who is the general manager of POETIKA AS?

Irina Ervik is registered as general manager of POETIKA AS.

Where is POETIKA AS based?

POETIKA AS has its business address in Ottestad.

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.