BIZTRAC BETA
Retail sale of information and communication equipment

BRS HOLDING AS

Org. no. 988131938 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −117,000
Equity NOK 67.8m
Incorporated 2005
Share capital NOK 12.4m

Signals

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

BRS HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988131938. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2005. Registered share capital is NOK 12.4m, divided into 12883 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −117,000
Equity
NOK 67.8m
Est. value
NOK 162.4m

Financial health · 2024

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

Who owns BRS HOLDING AS?

HANS JØRGEN SÆTHER
BRS HOLDING AS
· NOK −117,000 profit

BRS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRS HOLDING AS own?

BRS HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BRS HOLDING AS

Who owns BRS HOLDING AS?

HANS JØRGEN SÆTHER is the largest registered owner, with 90.7%.

Who is the general manager of BRS HOLDING AS?

Hans Jørgen Sæther is registered as general manager of BRS HOLDING AS.

Where is BRS HOLDING AS based?

BRS HOLDING AS has its business address in Trondheim.

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.