BIZTRAC BETA
Uoppgitt

RIL SPILLERINVEST 1 AS

Org. no. 934920627 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −56,000
Equity NOK 3.0m
Incorporated 2025
Share capital NOK 60,000

Signals

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

RIL SPILLERINVEST 1 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934920627. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Investere i videreutvikling av Ranheim IL Fotball Topp og motta en andel av bruttoinntektene fra alle spillersalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −56,000
Equity
NOK 3.0m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns RIL SPILLERINVEST 1 AS?

RANHEIM IL FOTBALL TOPP
RIL SPILLERINVEST 1 AS
NOK 0 rev. · NOK −56,000 profit

RIL SPILLERINVEST 1 AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIL SPILLERINVEST 1 AS

Who owns RIL SPILLERINVEST 1 AS?

RANHEIM IL FOTBALL TOPP is the largest registered owner, with 50.0%.

What is the revenue of RIL SPILLERINVEST 1 AS?

RIL SPILLERINVEST 1 AS had revenue of NOK 0 in 2025.

Who is the general manager of RIL SPILLERINVEST 1 AS?

Andreas Munkvold Stålby is registered as general manager of RIL SPILLERINVEST 1 AS.

Where is RIL SPILLERINVEST 1 AS based?

RIL SPILLERINVEST 1 AS has its business address in Ranheim.

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.