BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

SITSKI NORWAY AS

Org. no. 997557409 Limited company (AS) Hamar Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 2.1m
Equity NOK 1.9m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SITSKI NORWAY AS is registered as a limited company in Hamar, Innlandet with organisation number 997557409. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import, produksjon og salg av utstyr til funksjonshemmede, rådgivning og deltagelse i andre virksomheter gjennom utleie av personell til kurs og annen forefallende virksomhet. Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 2.1m
Equity
NOK 1.9m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns SITSKI NORWAY AS?

IMERSLUND HOLDING AS
SITSKI NORWAY AS
NOK 6.9m rev. · NOK 2.1m profit

SITSKI NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SITSKI NORWAY AS

Who owns SITSKI NORWAY AS?

IMERSLUND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SITSKI NORWAY AS?

SITSKI NORWAY AS had revenue of NOK 6.9m in 2024.

Where is SITSKI NORWAY AS based?

SITSKI NORWAY AS has its business address in Ingeberg.

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.