biztrac. BETA
COMPANY REGISTER PROFILE
989455893 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

BIEN BAR AS

Org. no. 989455893 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 7.1m
Operating profit NOK 220,000
Equity NOK 358,000
Incorporated 2006
Employees 12
Share capital NOK 107,000

BIEN BAR AS is registered as a limited company in Bergen, Vestland with organisation number 989455893. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2006 and has 12 registered employees. Registered share capital is NOK 107,000, divided into 965 shares. The company's stated purpose is: “Salg av mat/drikke og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.1m in revenue and NOK 220,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.1m
▼ −2 %
Operating profit
NOK 220,000
▲ +569 %
Equity
NOK 358,000
▲ +456 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
8.2%
Satisfactory
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns BIEN BAR AS?

BIEN BAR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIEN BAR AS

Who owns BIEN BAR AS?

BIEN HOLDING AS is the largest registered owner, with 90.2%.

What is the revenue of BIEN BAR AS?

BIEN BAR AS had revenue of NOK 7.1m in 2025.

Who is the general manager of BIEN BAR AS?

Petter Hellesen Lidal is registered as general manager of BIEN BAR AS.

Where is BIEN BAR AS based?

BIEN BAR AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.