BIZTRAC BETA
Wholesale of beverages

BARRAMON AS

Org. no. 917537003 Limited company (AS) Asker Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 191,000
Equity NOK 280,000
Incorporated 2016
Share capital NOK 30,000

BARRAMON AS is registered as a limited company in Asker, Akershus with organisation number 917537003. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Import og salg av alkoholholdig drikker samt delikatesseprodukter for salg til butikk og restauranter. Selskapets formål er også å utøve eierskap over restauranter og butikker samt forvalte eventuelle overskudd fra disse ved kjøp av eiendom, aksjer og andre verdipapirer. ”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 191,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 191,000
Equity
NOK 280,000
Est. value
NOK 689,000

Financial health · 2025

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

Who owns BARRAMON AS?

OSLO YACHT SERVICE AS
BARRAMON AS
NOK 1.5m rev. · NOK 191,000 profit

BARRAMON AS has 2 registered shareholders:

All shareholders and roles →

Group structure

BARRAMON AS er morselskap for 1 datterselskap:

Frequently asked questions about BARRAMON AS

Who owns BARRAMON AS?

OSLO YACHT SERVICE AS is the largest registered owner, with 50.0%.

What is the revenue of BARRAMON AS?

BARRAMON AS had revenue of NOK 1.5m in 2025.

Who is the general manager of BARRAMON AS?

Tore Kristian Tofte is registered as general manager of BARRAMON AS.

Where is BARRAMON AS based?

BARRAMON AS has its business address in Nesøya.

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.