biztrac. BETA
COMPANY REGISTER PROFILE
931765434 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other specialised construction activities n.e.c.

BRØYT HOLDING AS

Org. no. 931765434 Limited company (AS) Time Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −312,000
Equity NOK 35.8m
Incorporated 2023
Share capital NOK 450,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−312k kr).

BRØYT HOLDING AS is registered as a limited company in Time, Rogaland with organisation number 931765434. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2023. Registered share capital is NOK 450,000, divided into 30000 shares. The company's stated purpose is: “Eie og investere i aksjer og andeler i andre selskaper og virksomheter, herunder deltakelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”.

Former names: TREKK 2315 AS

Key figures · 2024

Operating profit
NOK −312,000
▼ −982 %
Equity
NOK 35.8m
▼ −14 %
Est. value
NOK 36.7m

Financial health · 2024

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
1.2%
Weak
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns BRØYT HOLDING AS?

BRØYT HOLDING AS
· NOK −312,000 profit

BRØYT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRØYT HOLDING AS own?

BRØYT HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BRØYT HOLDING AS

Who owns BRØYT HOLDING AS?

JÆRENTREPRENØR AS is the largest registered owner, with 50.0%.

Who is the general manager of BRØYT HOLDING AS?

Espen Langenes Kyllingstad is registered as general manager of BRØYT HOLDING AS.

Where is BRØYT HOLDING AS based?

BRØYT HOLDING AS has its business address in Bryne.

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.