BIZTRAC BETA
Other support activities to arts and performing arts

MA LYD OG LYS AS

Org. no. 935781760 Limited company (AS) Bamble Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 546,000
Operating profit NOK 140,000
Equity NOK 142,000
Incorporated 2025
Share capital NOK 30,000

MA LYD OG LYS AS is registered as a limited company in Bamble, Telemark with organisation number 935781760. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie og rigging av utstyr til lys- og lydoppdrag. Teknisk bistand og drift for bruk av lyd- og lysutstyr samt generelt salg av vaktmestertjenester og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 546,000 in revenue and NOK 140,000 in operating profit.

Key figures · 2025

Revenue
NOK 546,000
Operating profit
NOK 140,000
Equity
NOK 142,000
Est. value
NOK 561,000

Financial health · 2025

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

Who owns MA LYD OG LYS AS?

MARTIN ANDREASSEN
MA LYD OG LYS AS
NOK 546,000 rev. · NOK 140,000 profit

MA LYD OG LYS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MA LYD OG LYS AS

Who owns MA LYD OG LYS AS?

MARTIN ANDREASSEN is the largest registered owner, with 100.0%.

What is the revenue of MA LYD OG LYS AS?

MA LYD OG LYS AS had revenue of NOK 546,000 in 2025.

Who is the general manager of MA LYD OG LYS AS?

Martin Andreassen is registered as general manager of MA LYD OG LYS AS.

Where is MA LYD OG LYS AS based?

MA LYD OG LYS AS has its business address in Langesund.

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.