biztrac. BETA
COMPANY REGISTER PROFILE
835459322 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other content distribution activities

BROENTECH SENTINEL AS

Org. no. 835459322 Limited company (AS) Horten Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 7,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BROENTECH SENTINEL AS is registered as a limited company in Horten, Vestfold with organisation number 835459322. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Skal utvikle, levere og vedlikeholde teknologiske løsninger og tjenester for næringslivet. Virksomheten omfatter også konsulentvirksomhet, forskning og utvikling, samt investeringer i og drift av annen virksomhet som naturlig knytter seg til dette.”.

Key figures · 2025

Operating profit
NOK −23,000
Equity
NOK 7,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns BROENTECH SENTINEL AS?

BROENTECH SENTINEL AS
· NOK −23,000 profit

BROENTECH SENTINEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROENTECH SENTINEL AS

Who owns BROENTECH SENTINEL AS?

Stian Broen is the largest registered owner, with 100.0%.

Who is the general manager of BROENTECH SENTINEL AS?

Stian Broen is registered as general manager of BROENTECH SENTINEL AS.

Where is BROENTECH SENTINEL AS based?

BROENTECH SENTINEL AS has its business address in Åsgårdstrand.

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.