biztrac. BETA
COMPANY REGISTER PROFILE
833204122 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of call centres

RIMELIG AS

Org. no. 833204122 Limited company (AS) Trondheim Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK −20,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−20k kr).

RIMELIG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 833204122. The business is classified under activities of call centres (NACE 82.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salgsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −6,000
▲ +82 %
Equity
NOK −20,000
▼ −147 %

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-2.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RIMELIG AS?

RIMELIG AS
NOK 0 rev. · NOK −6,000 profit

RIMELIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RIMELIG AS own?

RIMELIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RIMELIG AS

Who owns RIMELIG AS?

Fredrik Oftedal is the largest registered owner, with 100.0%.

What is the revenue of RIMELIG AS?

RIMELIG AS had revenue of NOK 0 in 2025.

Who is the general manager of RIMELIG AS?

Fredrik Oftedal is registered as general manager of RIMELIG AS.

Where is RIMELIG AS based?

RIMELIG AS has its business address in Trondheim.

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.