BIZTRAC BETA
COMPANY REGISTER PROFILE
927992914 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

BRENDHAGEN BYGG AS

Org. no. 927992914 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Equity NOK 111,000
Incorporated 2021
Share capital NOK 30,000

BRENDHAGEN BYGG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 927992914. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrervirksomhet.”.

Key figures · 2025

Equity
NOK 111,000
Est. value
NOK 131,000

Financial health · 2025

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

Who owns BRENDHAGEN BYGG AS?

BRENDHAGEN BYGG AS

BRENDHAGEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRENDHAGEN BYGG AS own?

BRENDHAGEN BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRENDHAGEN BYGG AS

Who owns BRENDHAGEN BYGG AS?

MARIUS BRENDHAGEN is the largest registered owner, with 100.0%.

Who is the general manager of BRENDHAGEN BYGG AS?

Marius Brendhagen is registered as general manager of BRENDHAGEN BYGG AS.

Where is BRENDHAGEN BYGG AS based?

BRENDHAGEN BYGG AS has its business address in Sandefjord.

Property

Business address Gresshoppeveien 8, 3218 Sandefjord
Cadastral unit 3907-88/54/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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