BIZTRAC BETA
Beverage serving activities

DRÅPEN SOLSIDEN AS

Org. no. 990574243 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 21.3m
Operating profit NOK 983,000
Equity NOK −1.3m
Incorporated 2006
Employees 43
Share capital NOK 385,000

Signals

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

DRÅPEN SOLSIDEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 990574243. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2006 and has 43 registered employees. Registered share capital is NOK 385,000, divided into 385 shares. The company's stated purpose is: “Drift av bar, pub, nattklubb”. The most recent filed accounts, for the 2024 financial year, show NOK 21.3m in revenue and NOK 983,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.3m
Operating profit
NOK 983,000
Equity
NOK −1.3m
Est. value
NOK 5.1m

Financial health · 2024

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

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

Who owns DRÅPEN SOLSIDEN AS?

JTF AS
DRÅPEN SOLSIDEN AS
NOK 21.3m rev. · NOK 983,000 profit

DRÅPEN SOLSIDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRÅPEN SOLSIDEN AS

Who owns DRÅPEN SOLSIDEN AS?

JTF AS is the largest registered owner, with 100.0%.

What is the revenue of DRÅPEN SOLSIDEN AS?

DRÅPEN SOLSIDEN AS had revenue of NOK 21.3m in 2024.

Who is the general manager of DRÅPEN SOLSIDEN AS?

Jan-Tore Fladvad is registered as general manager of DRÅPEN SOLSIDEN AS.

Where is DRÅPEN SOLSIDEN AS based?

DRÅPEN SOLSIDEN 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.