BIZTRAC BETA
Motion picture, video and television programme production activities

RAMPELYS AS

Org. no. 940269490 Limited company (AS) Sortland Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 111,000
Operating profit NOK −27,000
Equity NOK 197,000
Incorporated 1986
Share capital NOK 200,000

Signals

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

RAMPELYS AS is registered as a limited company in Sortland, Nordland with organisation number 940269490. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 1986. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Informasjonsvirksomhet, samt annen virksomhet som naturlig faller inn under dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 111,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 111,000
Operating profit
NOK −27,000
Equity
NOK 197,000
Est. value
NOK 214,000

Financial health · 2024

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

Who owns RAMPELYS AS?

EVA CHARLOTTE NILSEN
RAMPELYS AS
NOK 111,000 rev. · NOK −27,000 profit

RAMPELYS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAMPELYS AS

Who owns RAMPELYS AS?

EVA CHARLOTTE NILSEN is the largest registered owner, with 52.0%.

What is the revenue of RAMPELYS AS?

RAMPELYS AS had revenue of NOK 111,000 in 2024.

Who is the general manager of RAMPELYS AS?

Eva Charlotte Nilsen is registered as general manager of RAMPELYS AS.

Where is RAMPELYS AS based?

RAMPELYS AS has its business address in Sortland.

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.