BIZTRAC BETA
Other technical consultancy

RAMEKO AS

Org. no. 988510173 Limited company (AS) Porsgrunn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −46,000
Equity NOK 362,000
Incorporated 2005
Share capital NOK 30,000

Signals

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

RAMEKO AS is registered as a limited company in Porsgrunn, Telemark with organisation number 988510173. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor energisektoren, samt investering i aksjer, fast eiendom samt helt eller delvis å delta i eller eie andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 362,000
Est. value
NOK 794,000

Financial health · 2025

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

Who owns RAMEKO AS?

ROLF SVAN AMUNDSEN
RAMEKO AS
NOK 0 rev. · NOK −46,000 profit

RAMEKO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAMEKO AS own?

RAMEKO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAMEKO AS

Who owns RAMEKO AS?

ROLF SVAN AMUNDSEN is the largest registered owner, with 100.0%.

What is the revenue of RAMEKO AS?

RAMEKO AS had revenue of NOK 0 in 2025.

Who is the general manager of RAMEKO AS?

Rolf Svan Amundsen is registered as general manager of RAMEKO AS.

Where is RAMEKO AS based?

RAMEKO AS has its business address in Porsgrunn.

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.