BIZTRAC BETA
Restaurant activities

SPOR AV NORD AS

Org. no. 924329203 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 12.1m
Operating profit NOK 360,000
Equity NOK −1.9m
Incorporated 2019
Employees 37
Share capital NOK 400,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,9 mill kr).

SPOR AV NORD AS is registered as a limited company in Oslo, Oslo with organisation number 924329203. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 37 registered employees. Registered share capital is NOK 400,000, divided into 100 shares. The company's stated purpose is: “Drift av serveringssted, kunsthandel og salg av interiør (vintage/antikk).”. The most recent filed accounts, for the 2024 financial year, show NOK 12.1m in revenue and NOK 360,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.1m
Operating profit
NOK 360,000
Equity
NOK −1.9m
Est. value
NOK 2.3m

Financial health · 2024

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

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

Who owns SPOR AV NORD AS?

SIV HEIDI BREIVIK
SPOR AV NORD AS
NOK 12.1m rev. · NOK 360,000 profit

SPOR AV NORD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPOR AV NORD AS

Who owns SPOR AV NORD AS?

SIV HEIDI BREIVIK is the largest registered owner, with 40.0%.

What is the revenue of SPOR AV NORD AS?

SPOR AV NORD AS had revenue of NOK 12.1m in 2024.

Who is the general manager of SPOR AV NORD AS?

Mia Hakalahti Eilertsen is registered as general manager of SPOR AV NORD AS.

Where is SPOR AV NORD AS based?

SPOR AV NORD AS has its business address in Oslo.

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.