BIZTRAC BETA
Restaurant activities

RUSTIKK HARSTAD AS

Org. no. 917995141 Limited company (AS) Narvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK −338,000
Equity NOK −5.0m
Incorporated 2016
Employees 19
Share capital NOK 800,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−338k kr).

RUSTIKK HARSTAD AS is registered as a limited company in Narvik, Nordland with organisation number 917995141. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016 and has 19 registered employees. Registered share capital is NOK 800,000, divided into 100 shares. The company's stated purpose is: “Bakeri, kafe og andre produkter/tjenester som naturlig hører sammen med dette, herunder også å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK −338,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK −338,000
Equity
NOK −5.0m

Financial health · 2025

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

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

Who owns RUSTIKK HARSTAD AS?

LUNSJ AS
RUSTIKK HARSTAD AS
NOK 6.1m rev. · NOK −338,000 profit

RUSTIKK HARSTAD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUSTIKK HARSTAD AS

Who owns RUSTIKK HARSTAD AS?

LUNSJ AS is the largest registered owner, with 51.0%.

What is the revenue of RUSTIKK HARSTAD AS?

RUSTIKK HARSTAD AS had revenue of NOK 6.1m in 2025.

Where is RUSTIKK HARSTAD AS based?

RUSTIKK HARSTAD AS has its business address in Narvik.

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.