BIZTRAC BETA
Computer consultancy and computer facilities management activities

NILTO AS

Org. no. 919228326 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −20,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

NILTO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 919228326. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester, salg av varer, produktutvikling, webdesign, it-tjenester og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK −20,000

Financial health · 2024

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

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

Who owns NILTO AS?

TORE NILSEN
NILTO AS
· NOK −3,000 profit

NILTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NILTO AS

Who owns NILTO AS?

TORE NILSEN is the largest registered owner, with 100.0%.

Who is the general manager of NILTO AS?

Tore Nilsen is registered as general manager of NILTO AS.

Where is NILTO AS based?

NILTO AS has its business address in Tønsberg.

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.