BIZTRAC BETA
Sound recording and music publishing activities

REIN LYD AS

Org. no. 919626720 Limited company (AS) Nesseby Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −268,000
Equity NOK 208,000
Incorporated 2017
Share capital NOK 105,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−268k kr).

REIN LYD AS is registered as a limited company in Nesseby, Finnmark with organisation number 919626720. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2017. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Drive virksomhet innen for lydproduksjon, lyd til bilde, musikk- og medie-produksjon, samt oppgaver som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −268,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −268,000
Equity
NOK 208,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.4%
Good
Equity as a share of total capital

Who owns REIN LYD AS?

KIM-ERLING METHI JOHANSEN
REIN LYD AS
NOK 1.2m rev. · NOK −268,000 profit

REIN LYD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REIN LYD AS

Who owns REIN LYD AS?

KIM-ERLING METHI JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of REIN LYD AS?

REIN LYD AS had revenue of NOK 1.2m in 2024.

Who is the general manager of REIN LYD AS?

Kim-Erling Methi Johansen is registered as general manager of REIN LYD AS.

Where is REIN LYD AS based?

REIN LYD AS has its business address in Varangerbotn.

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.