BIZTRAC BETA
Manufacture of beer

RAMP BRYGG AS

Org. no. 919896620 Limited company (AS) Aure Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 348,000
Operating profit NOK −13,000
Equity NOK −78,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−78k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

RAMP BRYGG AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 919896620. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilvirking av eget øl og andre alkoholholdige drikkevarer opp til 22%, samt salg og servering av disse varene.”. The most recent filed accounts, for the 2025 financial year, show NOK 348,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 348,000
Operating profit
NOK −13,000
Equity
NOK −78,000

Financial health · 2025

Liquidity
4.53
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-84.9%
Weak
Equity as a share of total capital

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

Who owns RAMP BRYGG AS?

Mats Torset
RAMP BRYGG AS
NOK 348,000 rev. · NOK −13,000 profit

RAMP BRYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAMP BRYGG AS

Who owns RAMP BRYGG AS?

Mats Torset is the largest registered owner, with 50.0%.

What is the revenue of RAMP BRYGG AS?

RAMP BRYGG AS had revenue of NOK 348,000 in 2025.

Who is the general manager of RAMP BRYGG AS?

Mats Torset is registered as general manager of RAMP BRYGG AS.

Where is RAMP BRYGG AS based?

RAMP BRYGG AS has its business address in Vihals.

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.