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

RAMMEVERKSTEDET AS

Org. no. 930606022 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 111,000
Equity NOK 192,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAMMEVERKSTEDET AS is registered as a limited company in Bergen, Vestland with organisation number 930606022. 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 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av rammer og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 111,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 111,000
Equity
NOK 192,000
Est. value
NOK 528,000

Financial health · 2024

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

Who owns RAMMEVERKSTEDET AS?

BC HOLDING INVEST AS
RAMMEVERKSTEDET AS
NOK 1.9m rev. · NOK 111,000 profit

RAMMEVERKSTEDET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAMMEVERKSTEDET AS

Who owns RAMMEVERKSTEDET AS?

BC HOLDING INVEST AS is the largest registered owner, with 80.0%.

What is the revenue of RAMMEVERKSTEDET AS?

RAMMEVERKSTEDET AS had revenue of NOK 1.9m in 2024.

Where is RAMMEVERKSTEDET AS based?

RAMMEVERKSTEDET AS has its business address in Bergen.

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.