BIZTRAC BETA
Computer consultancy and computer facilities management activities

SIN4U AS

Org. no. 916093438 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 885,000
Operating profit NOK 582,000
Equity NOK −1.4m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).

SIN4U AS is registered as a limited company in Asker, Akershus with organisation number 916093438. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av informasjonsteknologi og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 885,000 in revenue and NOK 582,000 in operating profit.

Key figures · 2024

Revenue
NOK 885,000
Operating profit
NOK 582,000
Equity
NOK −1.4m
Est. value
NOK 2.5m

Financial health · 2024

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

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

Who owns SIN4U AS?

TOR SANDNES AS
SIN4U AS
NOK 885,000 rev. · NOK 582,000 profit

SIN4U AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIN4U AS

Who owns SIN4U AS?

TOR SANDNES AS is the largest registered owner, with 75.0%.

What is the revenue of SIN4U AS?

SIN4U AS had revenue of NOK 885,000 in 2024.

Where is SIN4U AS based?

SIN4U AS has its business address in Nesøya.

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.