BIZTRAC BETA
Beverage serving activities

BAKGÅRDEN BAR AS

Org. no. 966747404 Limited company (AS) Kristiansand Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 13.1m
Operating profit NOK −1.1m
Equity NOK 655,000
Incorporated 1993
Employees 28
Share capital NOK 223,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

BAKGÅRDEN BAR AS is registered as a limited company in Kristiansand, Agder with organisation number 966747404. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 1993 and has 28 registered employees. Registered share capital is NOK 223,000, divided into 223 shares. The company's stated purpose is: “Bar, kurs- og restaurantvirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.1m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 13.1m
Operating profit
NOK −1.1m
Equity
NOK 655,000
Est. value
NOK 9.4m

Financial health · 2024

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns BAKGÅRDEN BAR AS?

BAKGÅRDEN HOLDING AS
BAKGÅRDEN BAR AS
NOK 13.1m rev. · NOK −1.1m profit

BAKGÅRDEN BAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BAKGÅRDEN BAR AS

Who owns BAKGÅRDEN BAR AS?

BAKGÅRDEN HOLDING AS is the largest registered owner, with 85.7%.

What is the revenue of BAKGÅRDEN BAR AS?

BAKGÅRDEN BAR AS had revenue of NOK 13.1m in 2024.

Who is the general manager of BAKGÅRDEN BAR AS?

Terje Solli is registered as general manager of BAKGÅRDEN BAR AS.

Where is BAKGÅRDEN BAR AS based?

BAKGÅRDEN BAR AS has its business address in Kristiansand S.

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.