biztrac. BETA
COMPANY REGISTER PROFILE
933673170 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BREWER HOLDING AS

Org. no. 933673170 Limited company (AS) Tønsberg Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −67,000
Equity NOK 1.6m
Incorporated 2024
Share capital NOK 75,000

Signals

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

BREWER HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 933673170. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 75,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −67,000
▼ −844 %
Equity
NOK 1.6m
▲ +6703 %
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns BREWER HOLDING AS?

BREWER HOLDING AS
· NOK −67,000 profit

BREWER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREWER HOLDING AS own?

BREWER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BREWER HOLDING AS

Who owns BREWER HOLDING AS?

Henriette Gran-Jansen Brewer is the largest registered owner, with 100.0%.

Who is the general manager of BREWER HOLDING AS?

Henriette Gran-Jansen Brewer is registered as general manager of BREWER HOLDING AS.

Where is BREWER HOLDING AS based?

BREWER HOLDING AS has its business address in Vear.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.