BIZTRAC BETA
Other support activities to arts and performing arts

NIDAROS LYD AS

Org. no. 935096588 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-17 Adresseendring registrert 2026-04-17.

NIDAROS LYD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935096588. 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 30000 shares. The company's stated purpose is: “Salg, prosjektering, installasjon og drift av lyd, lys, bilde og sceneinstallasjoner samt tilhørende tekniske løsninger og tjenester. Selskapet kan også drive utleie, service, rådgivning og annen virksomhet som står i naturlig sammenheng med dette, herunder investering i andre selskaper.”.

Key figures · 2025

Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NIDAROS LYD AS?

PRETOR ADVOKAT AS
NIDAROS LYD AS

NIDAROS LYD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIDAROS LYD AS

Who owns NIDAROS LYD AS?

PRETOR ADVOKAT AS is the largest registered owner, with 100.0%.

Who is the general manager of NIDAROS LYD AS?

Magnus Solum Galguften is registered as general manager of NIDAROS LYD AS.

Where is NIDAROS LYD AS based?

NIDAROS LYD AS has its business address in Heimdal.

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.