BIZTRAC BETA
Manufacture of other products of wood and articles of cork, straw and plaiting materials

PÅ RAMME ALVOR AS

Org. no. 918434755 Limited company (AS) Moss Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 29,000
Equity NOK 150,000
Incorporated 2017
Share capital NOK 30,000

PÅ RAMME ALVOR AS is registered as a limited company in Moss, Østfold with organisation number 918434755. The business is classified under manufacture of other products of wood and articles of cork, straw and plaiting materials (NACE 16.280). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rammeverksted, fotostudio, reklamebyrå, investering i fast eiendom og aksjer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 29,000
Equity
NOK 150,000
Est. value
NOK 187,000

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.7%
Good
Equity as a share of total capital

Who owns PÅ RAMME ALVOR AS?

CHRISTIAN CLAUSEN
PÅ RAMME ALVOR AS
NOK 1.5m rev. · NOK 29,000 profit

PÅ RAMME ALVOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PÅ RAMME ALVOR AS

Who owns PÅ RAMME ALVOR AS?

CHRISTIAN CLAUSEN is the largest registered owner, with 100.0%.

What is the revenue of PÅ RAMME ALVOR AS?

PÅ RAMME ALVOR AS had revenue of NOK 1.5m in 2025.

Who is the general manager of PÅ RAMME ALVOR AS?

Christian Clausen is registered as general manager of PÅ RAMME ALVOR AS.

Where is PÅ RAMME ALVOR AS based?

PÅ RAMME ALVOR AS has its business address in Moss.

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.