BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

RAMME OG TRYKK AS

Org. no. 934606302 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 75,000
Operating profit NOK −10,000
Equity NOK 117
Incorporated 2024
Share capital NOK 30,000

Signals

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

RAMME OG TRYKK AS is registered as a limited company in Bergen, Vestland with organisation number 934606302. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rammeverksted og butikk med salg av interiør og trykk.”. The most recent filed accounts, for the 2025 financial year, show NOK 75,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 75,000
Operating profit
NOK −10,000
Equity
NOK 117
Est. value
NOK 24,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RAMME OG TRYKK AS?

BOBL AS
RAMME OG TRYKK AS
NOK 75,000 rev. · NOK −10,000 profit

RAMME OG TRYKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAMME OG TRYKK AS

Who owns RAMME OG TRYKK AS?

BOBL AS is the largest registered owner, with 50.0%.

What is the revenue of RAMME OG TRYKK AS?

RAMME OG TRYKK AS had revenue of NOK 75,000 in 2025.

Who is the general manager of RAMME OG TRYKK AS?

Terje Bergsvik Knudsen is registered as general manager of RAMME OG TRYKK AS.

Where is RAMME OG TRYKK AS based?

RAMME OG TRYKK AS has its business address in Flaktveit.

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.