BIZTRAC BETA
Restaurant activities

SJEFSTROLL AS

Org. no. 916320701 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 907,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 86,000

SJEFSTROLL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916320701. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 86,000, divided into 86 shares. The company's stated purpose is: “Drive restaurant, pub, scene og være konsertarrangør, samt alt som naturlig hører til disse forretningsområdene inkludert investeringer i andre selskaper innenfor virksomhetsområdet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 907,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 907,000
Equity
NOK 1.1m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns SJEFSTROLL AS?

SJEFSTROLL AS
SJEFSTROLL AS
NOK 4.8m rev. · NOK 907,000 profit

SJEFSTROLL AS has 5 registered shareholders:

All shareholders and roles →

Which companies does SJEFSTROLL AS own?

SJEFSTROLL AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SJEFSTROLL AS

Who owns SJEFSTROLL AS?

SJEFSTROLL AS is the largest registered owner, with 27.9%.

What is the revenue of SJEFSTROLL AS?

SJEFSTROLL AS had revenue of NOK 4.8m in 2024.

Who is the general manager of SJEFSTROLL AS?

Joachim Rangø Andersen is registered as general manager of SJEFSTROLL AS.

Where is SJEFSTROLL AS based?

SJEFSTROLL AS has its business address in Trondheim.

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.