BIZTRAC BETA
COMPANY REGISTER PROFILE
933295753 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Non-specialised retail sale of predominately food, beverages or tobacco

BUTIKKDRIFT SJØLIE AS

Org. no. 933295753 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 21,000
Incorporated 2024
Employees 20
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

BUTIKKDRIFT SJØLIE AS is registered as a limited company in Oslo, Oslo with organisation number 933295753. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2024 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Drive virksomhet, herunder spill i kioskhandel med bredt vareutvalg med hovedvekt på næring- og nytelsesmidler.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK 21,000
Est. value
NOK 26,000

Financial health · 2024

Liquidity
15.56
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.6%
Weak
Equity as a share of total capital

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

Who owns BUTIKKDRIFT SJØLIE AS?

JENS ERIK SJØLIE
BUTIKKDRIFT SJØLIE AS
· NOK −3,000 profit

BUTIKKDRIFT SJØLIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUTIKKDRIFT SJØLIE AS

Who owns BUTIKKDRIFT SJØLIE AS?

JENS ERIK SJØLIE is the largest registered owner, with 100.0%.

Who is the general manager of BUTIKKDRIFT SJØLIE AS?

Jens Erik Sjølie is registered as general manager of BUTIKKDRIFT SJØLIE AS.

Where is BUTIKKDRIFT SJØLIE AS based?

BUTIKKDRIFT SJØLIE 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.