BIZTRAC BETA
Manufacture of plastic packing goods

BRIS NÆRINGSEIENDOM AS

Org. no. 992957409 Limited company (AS) Time Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 2.1m
Equity NOK 5.0m
Incorporated 2008
Share capital NOK 4.5m

Signals

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

BRIS NÆRINGSEIENDOM AS is registered as a limited company in Time, Rogaland with organisation number 992957409. The business is classified under manufacture of plastic packing goods (NACE 22.220). The company was incorporated in 2008. Registered share capital is NOK 4.5m, divided into 15000 shares. The company's stated purpose is: “Investere i aksjer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 2.1m
Equity
NOK 5.0m
Est. value
NOK 7.7m

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.5%
Good
Equity as a share of total capital

Who owns BRIS NÆRINGSEIENDOM AS?

DAHLE HOLDING AS
BRIS NÆRINGSEIENDOM AS
NOK 2.8m rev. · NOK 2.1m profit

BRIS NÆRINGSEIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BRIS NÆRINGSEIENDOM AS own?

BRIS NÆRINGSEIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRIS NÆRINGSEIENDOM AS

Who owns BRIS NÆRINGSEIENDOM AS?

DAHLE HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of BRIS NÆRINGSEIENDOM AS?

BRIS NÆRINGSEIENDOM AS had revenue of NOK 2.8m in 2025.

Where is BRIS NÆRINGSEIENDOM AS based?

BRIS NÆRINGSEIENDOM 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 15.06.2026.

Report a problem

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