BIZTRAC BETA
Retail sale of sports equipment

BRECOM AS

Org. no. 993048151 Limited company (AS) Nes Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 10.9m
Operating profit NOK −127,000
Equity NOK 770,000
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−127k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRECOM AS is registered as a limited company in Nes, Akershus with organisation number 993048151. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er å markedsføre og selge utstyr i forbindelse med jakt og friluftsliv. I tillegg hva styre finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.9m in revenue and NOK −127,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.9m
Operating profit
NOK −127,000
Equity
NOK 770,000
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns BRECOM AS?

BREEN INVEST AS
BRECOM AS
NOK 10.9m rev. · NOK −127,000 profit

BRECOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRECOM AS

Who owns BRECOM AS?

BREEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BRECOM AS?

BRECOM AS had revenue of NOK 10.9m in 2024.

Who is the general manager of BRECOM AS?

Torgeir Breen is registered as general manager of BRECOM AS.

Where is BRECOM AS based?

BRECOM AS has its business address in Årnes.

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.