BIZTRAC BETA
Leasing of intellectual property and similar products, except copyrighted works

RAMLO P&G AS

Org. no. 922224412 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −45,000
Equity NOK 302,000
Incorporated 2018
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAMLO P&G AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922224412. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Å eie og utnytte rettigheter til mineralske forekomster, samt annen virksomhet som naturlig står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −45,000
Equity
NOK 302,000
Est. value
NOK 434,000

Financial health · 2024

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

Who owns RAMLO P&G AS?

RAMLO HOLDING AS
RAMLO P&G AS
· NOK −45,000 profit

RAMLO P&G AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAMLO P&G AS own?

RAMLO P&G AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAMLO P&G AS

Who owns RAMLO P&G AS?

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

Who is the general manager of RAMLO P&G AS?

Tore Ramlo is registered as general manager of RAMLO P&G AS.

Where is RAMLO P&G AS based?

RAMLO P&G AS has its business address in Heimdal.

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.