BIZTRAC BETA
Arts creation activities in literature

NORSK INNSPILLINGSBYRÅ AS

Org. no. 979946481 Limited company (AS) Vestby Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 355,000
Operating profit NOK −22,000
Equity NOK 704,000
Incorporated 1998
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

NORSK INNSPILLINGSBYRÅ AS is registered as a limited company in Vestby, Akershus with organisation number 979946481. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 1998. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Produksjon og salg av tekster og melodier til musikk- og underholdningsbransjen, avholdelse av konsert-/turnevirksomhet og salg av relaterte varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 355,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 355,000
Operating profit
NOK −22,000
Equity
NOK 704,000
Est. value
NOK 644,000

Financial health · 2025

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

Who owns NORSK INNSPILLINGSBYRÅ AS?

ESPEN LIND
NORSK INNSPILLINGSBYRÅ AS
NOK 355,000 rev. · NOK −22,000 profit

NORSK INNSPILLINGSBYRÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK INNSPILLINGSBYRÅ AS

Who owns NORSK INNSPILLINGSBYRÅ AS?

ESPEN LIND is the largest registered owner, with 100.0%.

What is the revenue of NORSK INNSPILLINGSBYRÅ AS?

NORSK INNSPILLINGSBYRÅ AS had revenue of NOK 355,000 in 2025.

Where is NORSK INNSPILLINGSBYRÅ AS based?

NORSK INNSPILLINGSBYRÅ AS has its business address in Son.

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.