BIZTRAC BETA
Other software publishing

SUBLICITY AS

Org. no. 930795666 Limited company (AS) Karmøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 79,000
Operating profit NOK −3,000
Equity NOK 9,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SUBLICITY AS is registered as a limited company in Karmøy, Rogaland with organisation number 930795666. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av programvare og annet som naturlig faller sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 79,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 79,000
Operating profit
NOK −3,000
Equity
NOK 9,000
Est. value
NOK 137,000

Financial health · 2024

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

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

Who owns SUBLICITY AS?

EMIL BOROWIEC SOFTWARE AS
SUBLICITY AS
NOK 79,000 rev. · NOK −3,000 profit

SUBLICITY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUBLICITY AS

Who owns SUBLICITY AS?

EMIL BOROWIEC SOFTWARE AS is the largest registered owner, with 50.0%.

What is the revenue of SUBLICITY AS?

SUBLICITY AS had revenue of NOK 79,000 in 2024.

Who is the general manager of SUBLICITY AS?

Per Ejnar Thomsen is registered as general manager of SUBLICITY AS.

Where is SUBLICITY AS based?

SUBLICITY AS has its business address in Kvalavåg.

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.