BIZTRAC BETA
Business and other management consultancy activities

NIS KOM 2020 AS

Org. no. 924607793 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −3,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

NIS KOM 2020 AS is registered as a limited company in Bergen, Vestland with organisation number 924607793. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Regnskapstjenester, rådgiving og utleie av egen arbeidskraft, forvaltning av og investeringer i selskaper og eiendom, kjøp og salg av varer og tjenester herav også import og eksport. Samt deltakelse i andre selskaper med et hvert formål og annet som naturlig faller sammen med dette.”.

Key figures · 2024

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

Financial health · 2024

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

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

Who owns NIS KOM 2020 AS?

NILS INGE STEINSVÅG
NIS KOM 2020 AS
· NOK −21,000 profit

NIS KOM 2020 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIS KOM 2020 AS

Who owns NIS KOM 2020 AS?

NILS INGE STEINSVÅG is the largest registered owner, with 100.0%.

Who is the general manager of NIS KOM 2020 AS?

Nils Inge Steinsvåg is registered as general manager of NIS KOM 2020 AS.

Where is NIS KOM 2020 AS based?

NIS KOM 2020 AS has its business address in Bergen.

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.