BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

AS RAMSES

Org. no. 948891255 Limited company (AS) Lier Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK 2,000
Equity NOK 43.3m
Incorporated 1988
Share capital NOK 804,000

AS RAMSES is registered as a limited company in Lier, Buskerud with organisation number 948891255. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 1988. Registered share capital is NOK 804,000, divided into 200 shares. The company's stated purpose is: “Kjøp, utvikling og salg av eiendommer og drifts- midler samt hva hermed står i forbindelse, her- under å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 120,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK 2,000
Equity
NOK 43.3m
Est. value
NOK 20.6m

Financial health · 2024

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

Who owns AS RAMSES?

CARL-OVE FLATTUM SEIERSTAD
AS RAMSES
NOK 120,000 rev. · NOK 2,000 profit

AS RAMSES has 1 registered shareholder:

All shareholders and roles →

Which companies does AS RAMSES own?

AS RAMSES holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about AS RAMSES

Who owns AS RAMSES?

CARL-OVE FLATTUM SEIERSTAD is the largest registered owner, with 100.0%.

What is the revenue of AS RAMSES?

AS RAMSES had revenue of NOK 120,000 in 2024.

Who is the general manager of AS RAMSES?

Carl-Ove Flattum Seierstad is registered as general manager of AS RAMSES.

Where is AS RAMSES based?

AS RAMSES has its business address in Lier.

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.