biztrac. BETA
COMPANY REGISTER PROFILE
934898613 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of other personal and household goods

TOPP LYD & LYS AS

Org. no. 934898613 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 391,000
Operating profit NOK 181,000
Equity NOK 160,000
Incorporated 2025
Share capital NOK 30,000

TOPP LYD & LYS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934898613. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og utleie av lyd, lys og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 391,000 in revenue and NOK 181,000 in operating profit.

Key figures · 2025

Revenue
NOK 391,000
Operating profit
NOK 181,000
Equity
NOK 160,000
Est. value
NOK 661,000

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
61.0%
Very good
Equity as a share of total capital

Who owns TOPP LYD & LYS AS?

TOPP LYD & LYS AS
NOK 391,000 rev. · NOK 181,000 profit

TOPP LYD & LYS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPP LYD & LYS AS

Who owns TOPP LYD & LYS AS?

Håvard Klefstad is the largest registered owner, with 50.0%.

What is the revenue of TOPP LYD & LYS AS?

TOPP LYD & LYS AS had revenue of NOK 391,000 in 2025.

Who is the general manager of TOPP LYD & LYS AS?

Marius Neeraas Amdam is registered as general manager of TOPP LYD & LYS AS.

Where is TOPP LYD & LYS AS based?

TOPP LYD & LYS AS has its business address in Trondheim.

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.