BIZTRAC BETA
Sound recording and music publishing activities

LUFT RECORDINGS AS

Org. no. 933786110 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 266,000
Operating profit NOK 110,000
Equity NOK −9,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).

LUFT RECORDINGS AS is registered as a limited company in Bærum, Akershus with organisation number 933786110. 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 100 shares. The company's stated purpose is: “Musikkproduksjonsselskap, label og management.”. The most recent filed accounts, for the 2025 financial year, show NOK 266,000 in revenue and NOK 110,000 in operating profit.

Key figures · 2025

Revenue
NOK 266,000
Operating profit
NOK 110,000
Equity
NOK −9,000
Est. value
NOK 570,000

Financial health · 2025

Liquidity
10.43
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.7%
Weak
Equity as a share of total capital

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

Who owns LUFT RECORDINGS AS?

LUFT HOLDING AS
LUFT RECORDINGS AS
NOK 266,000 rev. · NOK 110,000 profit

LUFT RECORDINGS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUFT RECORDINGS AS

Who owns LUFT RECORDINGS AS?

LUFT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LUFT RECORDINGS AS?

LUFT RECORDINGS AS had revenue of NOK 266,000 in 2025.

Who is the general manager of LUFT RECORDINGS AS?

Andrew Murray Baardsen is registered as general manager of LUFT RECORDINGS AS.

Where is LUFT RECORDINGS AS based?

LUFT RECORDINGS AS has its business address in Sandvika.

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.