BIZTRAC BETA
Public relations and communication activities

WORSØ KOMMUNIKASJON AS

Org. no. 933380556 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 452,000
Operating profit NOK −529,000
Equity NOK 222,000
Incorporated 2024
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−529k kr).

WORSØ KOMMUNIKASJON AS is registered as a limited company in Stavanger, Rogaland with organisation number 933380556. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Tilby PR og kommunikasjonstjenester, inkludert, men ikke begrenset til, strategisk kommunikasjon, medieforbindelser, krisekommunikasjon, omdømmebygging og andre relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 452,000 in revenue and NOK −529,000 in operating profit.

Key figures · 2024

Revenue
NOK 452,000
Operating profit
NOK −529,000
Equity
NOK 222,000
Est. value
NOK 583,000

Financial health · 2024

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

Who owns WORSØ KOMMUNIKASJON AS?

SYKT BRA AS
WORSØ KOMMUNIKASJON AS
NOK 452,000 rev. · NOK −529,000 profit

WORSØ KOMMUNIKASJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WORSØ KOMMUNIKASJON AS

Who owns WORSØ KOMMUNIKASJON AS?

SYKT BRA AS is the largest registered owner, with 80.0%.

What is the revenue of WORSØ KOMMUNIKASJON AS?

WORSØ KOMMUNIKASJON AS had revenue of NOK 452,000 in 2024.

Where is WORSØ KOMMUNIKASJON AS based?

WORSØ KOMMUNIKASJON AS has its business address in Stavanger.

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.