BIZTRAC BETA
Sound recording and music publishing activities

LYSKESTREKK RECORDS AS

Org. no. 933710394 Limited company (AS) Nordre Follo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 592,000
Operating profit NOK 218,000
Equity NOK 195,000
Incorporated 2024
Share capital NOK 30,000

LYSKESTREKK RECORDS AS is registered as a limited company in Nordre Follo, Akershus with organisation number 933710394. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Plateselskap og artistbooking. Konserter, Salg og trykk av musikk på vinyl og digitalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 592,000 in revenue and NOK 218,000 in operating profit.

Key figures · 2024

Revenue
NOK 592,000
Operating profit
NOK 218,000
Equity
NOK 195,000
Est. value
NOK 975,000

Financial health · 2024

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

Who owns LYSKESTREKK RECORDS AS?

TORBJØRN LARSEN BRUNVAND
LYSKESTREKK RECORDS AS
NOK 592,000 rev. · NOK 218,000 profit

LYSKESTREKK RECORDS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSKESTREKK RECORDS AS

Who owns LYSKESTREKK RECORDS AS?

TORBJØRN LARSEN BRUNVAND is the largest registered owner, with 100.0%.

What is the revenue of LYSKESTREKK RECORDS AS?

LYSKESTREKK RECORDS AS had revenue of NOK 592,000 in 2024.

Who is the general manager of LYSKESTREKK RECORDS AS?

Torbjørn Larsen Brunvand is registered as general manager of LYSKESTREKK RECORDS AS.

Where is LYSKESTREKK RECORDS AS based?

LYSKESTREKK RECORDS AS has its business address in Kolbotn.

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.