BIZTRAC BETA
Sound recording and music publishing activities

NIORD LYDFABRIKK AS

Org. no. 934893891 Limited company (AS) Indre Østfold Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 71,000
Operating profit NOK 13,000
Equity NOK 35,000
Incorporated 2024
Share capital NOK 30,000

NIORD LYDFABRIKK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 934893891. 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 30 shares. The company's stated purpose is: “Lydstudio, produsere musikk, utleie av utstyr, booking av spillejobber og alt annet som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 71,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 71,000
Operating profit
NOK 13,000
Equity
NOK 35,000
Est. value
NOK 102,000

Financial health · 2025

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

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

Who owns NIORD LYDFABRIKK AS?

KNUT NIORD RØSAND
NIORD LYDFABRIKK AS
NOK 71,000 rev. · NOK 13,000 profit

NIORD LYDFABRIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIORD LYDFABRIKK AS

Who owns NIORD LYDFABRIKK AS?

KNUT NIORD RØSAND is the largest registered owner, with 100.0%.

What is the revenue of NIORD LYDFABRIKK AS?

NIORD LYDFABRIKK AS had revenue of NOK 71,000 in 2025.

Who is the general manager of NIORD LYDFABRIKK AS?

Knut Niord Røsand is registered as general manager of NIORD LYDFABRIKK AS.

Where is NIORD LYDFABRIKK AS based?

NIORD LYDFABRIKK AS has its business address in Askim.

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.