BIZTRAC BETA
Development of building projects

BRYNEPORTEN AS

Org. no. 886852592 Limited company (AS) Stavanger Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 706,000
Operating profit NOK 353,000
Equity NOK 3.0m
Incorporated 2004
Share capital NOK 1.3m

Signals

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

BRYNEPORTEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 886852592. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004. Registered share capital is NOK 1.3m, divided into 12900 shares. The company's stated purpose is: “Erverv, utvikle, drift, salg og utleie av fast eiendom samt deltakelse i andre prosjekter og selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 706,000 in revenue and NOK 353,000 in operating profit.

Key figures · 2024

Revenue
NOK 706,000
Operating profit
NOK 353,000
Equity
NOK 3.0m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns BRYNEPORTEN AS?

SVANEDAL AS
BRYNEPORTEN AS
NOK 706,000 rev. · NOK 353,000 profit

BRYNEPORTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYNEPORTEN AS

Who owns BRYNEPORTEN AS?

SVANEDAL AS is the largest registered owner, with 100.0%.

What is the revenue of BRYNEPORTEN AS?

BRYNEPORTEN AS had revenue of NOK 706,000 in 2024.

Who is the general manager of BRYNEPORTEN AS?

John Egil Hatlevik is registered as general manager of BRYNEPORTEN AS.

Where is BRYNEPORTEN AS based?

BRYNEPORTEN AS has its business address in Stavanger.

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.