BIZTRAC BETA
General cleaning of buildings

ISSY AS

Org. no. 918440461 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK −190,000
Equity NOK −115,000
Incorporated 2017
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−115k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−190k kr).

ISSY AS is registered as a limited company in Drammen, Buskerud with organisation number 918440461. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2017 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er basert på renhold, både hos private og offentlige lokaler samt import/salg av klær.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK −190,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK −190,000
Equity
NOK −115,000

Financial health · 2024

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

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

Who owns ISSY AS?

KINGA JOANNA KOSOWSKA
ISSY AS
NOK 3.9m rev. · NOK −190,000 profit

ISSY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISSY AS

Who owns ISSY AS?

KINGA JOANNA KOSOWSKA is the largest registered owner, with 100.0%.

What is the revenue of ISSY AS?

ISSY AS had revenue of NOK 3.9m in 2024.

Who is the general manager of ISSY AS?

Kinga Joanna Kosowska is registered as general manager of ISSY AS.

Where is ISSY AS based?

ISSY AS has its business address in Drammen.

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.