BIZTRAC BETA
Rental and leasing of other personal and household goods

HELGELAND LYDSERVICE AS

Org. no. 916148224 Limited company (AS) Alstahaug Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 262,000
Operating profit NOK 40,000
Equity NOK 104,000
Incorporated 2015
Share capital NOK 30,000

HELGELAND LYDSERVICE AS is registered as a limited company in Alstahaug, Nordland with organisation number 916148224. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie og salg av lydutstyr, konsulenttjenester, utleie av lysanlegg og dertilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 262,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 262,000
Operating profit
NOK 40,000
Equity
NOK 104,000
Est. value
NOK 188,000

Financial health · 2024

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

Who owns HELGELAND LYDSERVICE AS?

HÅKON FLATØY
HELGELAND LYDSERVICE AS
NOK 262,000 rev. · NOK 40,000 profit

HELGELAND LYDSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELGELAND LYDSERVICE AS

Who owns HELGELAND LYDSERVICE AS?

HÅKON FLATØY is the largest registered owner, with 100.0%.

What is the revenue of HELGELAND LYDSERVICE AS?

HELGELAND LYDSERVICE AS had revenue of NOK 262,000 in 2024.

Who is the general manager of HELGELAND LYDSERVICE AS?

Håkon Flatøy is registered as general manager of HELGELAND LYDSERVICE AS.

Where is HELGELAND LYDSERVICE AS based?

HELGELAND LYDSERVICE AS has its business address in Tjøtta.

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.