biztrac. BETA
COMPANY REGISTER PROFILE
935518245 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

RTM SOLUTIONS AS

Org. no. 935518245 Limited company (AS) Kongsvinger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 358,000
Operating profit NOK 133,000
Equity NOK 196,000
Incorporated 2025
Share capital NOK 400,000

Signals

1 flags
  • Nylig endring 2026-06-08 Aksjekapital registrert 2026-06-08.

RTM SOLUTIONS AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 935518245. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 400,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom og forvaltning av denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 358,000 in revenue and NOK 133,000 in operating profit.

Key figures · 2025

Revenue
NOK 358,000
Operating profit
NOK 133,000
Equity
NOK 196,000
Est. value
NOK 286,000

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
7.0%
Weak
Equity as a share of total capital

Who owns RTM SOLUTIONS AS?

RTM SOLUTIONS AS
NOK 358,000 rev. · NOK 133,000 profit

RTM SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RTM SOLUTIONS AS

Who owns RTM SOLUTIONS AS?

SPETALS VERK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RTM SOLUTIONS AS?

RTM SOLUTIONS AS had revenue of NOK 358,000 in 2025.

Who is the general manager of RTM SOLUTIONS AS?

Eivind Magnus Jonassen is registered as general manager of RTM SOLUTIONS AS.

Where is RTM SOLUTIONS AS based?

RTM SOLUTIONS AS has its business address in Kongsvinger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.