BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

NES KIOSK AS

Org. no. 917965919 Limited company (AS) Nes Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 6.5m
Operating profit NOK 688,000
Equity NOK −501,000
Incorporated 2016
Employees 10
Share capital NOK 530,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−501k kr).

NES KIOSK AS is registered as a limited company in Nes, Akershus with organisation number 917965919. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2016 and has 10 registered employees. Registered share capital is NOK 530,000, divided into 100 shares. The company's stated purpose is: “Kioskvirksomhet og salg av kioskvarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.5m in revenue and NOK 688,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.5m
Operating profit
NOK 688,000
Equity
NOK −501,000
Est. value
NOK 3.6m

Financial health · 2024

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

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

Who owns NES KIOSK AS?

MAHENDRAN KARTHIGESU
NES KIOSK AS
NOK 6.5m rev. · NOK 688,000 profit

NES KIOSK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NES KIOSK AS

Who owns NES KIOSK AS?

MAHENDRAN KARTHIGESU is the largest registered owner, with 100.0%.

What is the revenue of NES KIOSK AS?

NES KIOSK AS had revenue of NOK 6.5m in 2024.

Who is the general manager of NES KIOSK AS?

Mahendran Karthigesu is registered as general manager of NES KIOSK AS.

Where is NES KIOSK AS based?

NES KIOSK AS has its business address in Hvam.

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.