BIZTRAC BETA
Restaurant activities

SVELVIK PIZZADRIFT AS

Org. no. 918786155 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 60,000
Equity NOK 465,000
Incorporated 2017
Employees 10
Share capital NOK 100,000

SVELVIK PIZZADRIFT AS is registered as a limited company in Drammen, Buskerud with organisation number 918786155. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produsjon-, handel & serveringsvirksomhet med hovedvekt på pizzaprodukter samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 60,000
Equity
NOK 465,000
Est. value
NOK 434,000

Financial health · 2025

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

Who owns SVELVIK PIZZADRIFT AS?

SHIVANSHU SHARMA
SVELVIK PIZZADRIFT AS
NOK 3.2m rev. · NOK 60,000 profit

SVELVIK PIZZADRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVELVIK PIZZADRIFT AS

Who owns SVELVIK PIZZADRIFT AS?

SHIVANSHU SHARMA is the largest registered owner, with 50.0%.

What is the revenue of SVELVIK PIZZADRIFT AS?

SVELVIK PIZZADRIFT AS had revenue of NOK 3.2m in 2025.

Who is the general manager of SVELVIK PIZZADRIFT AS?

Shivanshu Sharma is registered as general manager of SVELVIK PIZZADRIFT AS.

Where is SVELVIK PIZZADRIFT AS based?

SVELVIK PIZZADRIFT AS has its business address in Svelvik.

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.