BIZTRAC BETA
Rental and operating of own or leased real estate

BRINGSBYGG AS

Org. no. 968820559 Limited company (AS) Stryn Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 996,000
Operating profit NOK 493,000
Equity NOK 3.6m
Incorporated 1994
Share capital NOK 3.3m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRINGSBYGG AS is registered as a limited company in Stryn, Vestland with organisation number 968820559. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 3.3m, divided into 3267 shares. The company's stated purpose is: “Eie eiendommen gnr. 57, bnr. 129 og 130, Stryn kommune, og leie ut byggningsmassen til eksterne leietakere.”. The most recent filed accounts, for the 2024 financial year, show NOK 996,000 in revenue and NOK 493,000 in operating profit.

Key figures · 2024

Revenue
NOK 996,000
Operating profit
NOK 493,000
Equity
NOK 3.6m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns BRINGSBYGG AS?

GRENDENE AS
BRINGSBYGG AS
NOK 996,000 rev. · NOK 493,000 profit

BRINGSBYGG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BRINGSBYGG AS own?

BRINGSBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRINGSBYGG AS

Who owns BRINGSBYGG AS?

GRENDENE AS is the largest registered owner, with 56.9%.

What is the revenue of BRINGSBYGG AS?

BRINGSBYGG AS had revenue of NOK 996,000 in 2024.

Where is BRINGSBYGG AS based?

BRINGSBYGG AS has its business address in Stryn.

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.