BIZTRAC BETA
Buying and selling of own real estate

RAGMO AS

Org. no. 993144762 Limited company (AS) Skaun Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −108,000
Equity NOK 19.3m
Incorporated 2008
Share capital NOK 100,000

Signals

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

RAGMO AS is registered as a limited company in Skaun, Trøndelag with organisation number 993144762. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i andre selskaper gjennom aksjer, andeler eller på annen måte, samt hva hermed står i sammenheng. Selskapet skal også kunne drive investering og drift av fast eiendom, samt forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −108,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −108,000
Equity
NOK 19.3m
Est. value
NOK 16.1m

Financial health · 2024

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

Who owns RAGMO AS?

RAGNHILD MØLMEN
RAGMO AS
NOK 10,000 rev. · NOK −108,000 profit

RAGMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAGMO AS

Who owns RAGMO AS?

RAGNHILD MØLMEN is the largest registered owner, with 100.0%.

What is the revenue of RAGMO AS?

RAGMO AS had revenue of NOK 10,000 in 2024.

Who is the general manager of RAGMO AS?

Ragnhild Mølmen is registered as general manager of RAGMO AS.

Where is RAGMO AS based?

RAGMO AS has its business address in Børsa.

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.