BIZTRAC BETA
Rental and leasing of other personal and household goods

BERGEN LYDUTLEIE AS

Org. no. 931919733 Limited company (AS) Askøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK −503,000
Equity NOK 5.3m
Incorporated 2023
Share capital NOK 4.6m

Signals

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

BERGEN LYDUTLEIE AS is registered as a limited company in Askøy, Vestland with organisation number 931919733. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2023. Registered share capital is NOK 4.6m, divided into 30 shares. The company's stated purpose is: “Utleie av lyd, lys og sceneutstyr og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK −503,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK −503,000
Equity
NOK 5.3m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns BERGEN LYDUTLEIE AS?

MUSIKKTIMEN AS
BERGEN LYDUTLEIE AS
NOK 7.0m rev. · NOK −503,000 profit

BERGEN LYDUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN LYDUTLEIE AS

Who owns BERGEN LYDUTLEIE AS?

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

What is the revenue of BERGEN LYDUTLEIE AS?

BERGEN LYDUTLEIE AS had revenue of NOK 7.0m in 2024.

Who is the general manager of BERGEN LYDUTLEIE AS?

Joachim Holmedal is registered as general manager of BERGEN LYDUTLEIE AS.

Where is BERGEN LYDUTLEIE AS based?

BERGEN LYDUTLEIE AS has its business address in Strusshamn.

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.