BIZTRAC BETA
Translation and interpretation activities

ONOMATOPOETIKON AS

Org. no. 925918695 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 181,000
Operating profit NOK 8,000
Equity NOK −33,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ONOMATOPOETIKON AS is registered as a limited company in Bergen, Vestland with organisation number 925918695. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oversettelse, språkvask og språktjenester. Kultur- og arrangementsproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 181,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 181,000
Operating profit
NOK 8,000
Equity
NOK −33,000
Est. value
NOK 78,000

Financial health · 2024

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

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

Who owns ONOMATOPOETIKON AS?

SUNNIVA VIK
ONOMATOPOETIKON AS
NOK 181,000 rev. · NOK 8,000 profit

ONOMATOPOETIKON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ONOMATOPOETIKON AS

Who owns ONOMATOPOETIKON AS?

SUNNIVA VIK is the largest registered owner, with 100.0%.

What is the revenue of ONOMATOPOETIKON AS?

ONOMATOPOETIKON AS had revenue of NOK 181,000 in 2024.

Who is the general manager of ONOMATOPOETIKON AS?

Sunniva Vik is registered as general manager of ONOMATOPOETIKON AS.

Where is ONOMATOPOETIKON AS based?

ONOMATOPOETIKON AS has its business address in Bergen.

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.