BIZTRAC BETA
Restaurant activities

INDI SPICE AS

Org. no. 914754070 Limited company (AS) Lørenskog Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 7.8m
Operating profit NOK −841,000
Equity NOK −549,000
Incorporated 2014
Employees 9
Share capital NOK 30,000

Signals

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

INDI SPICE AS is registered as a limited company in Lørenskog, Akershus with organisation number 914754070. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Mat og alkoholservering og restaurantdrift, med salg av tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.8m in revenue and NOK −841,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.8m
Operating profit
NOK −841,000
Equity
NOK −549,000

Financial health · 2024

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

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

Who owns INDI SPICE AS?

AMARPREET BAL
INDI SPICE AS
NOK 7.8m rev. · NOK −841,000 profit

INDI SPICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDI SPICE AS

Who owns INDI SPICE AS?

AMARPREET BAL is the largest registered owner, with 100.0%.

What is the revenue of INDI SPICE AS?

INDI SPICE AS had revenue of NOK 7.8m in 2024.

Where is INDI SPICE AS based?

INDI SPICE AS has its business address in Lørenskog.

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.