biztrac. BETA
COMPANY REGISTER PROFILE
988559059 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BJØRNØYGATEN AS

Org. no. 988559059 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −66,000
Equity NOK 16.4m
Incorporated 2005
Share capital NOK 38,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−66k kr).

BJØRNØYGATEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 988559059. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 38,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen administrativ og operativ ledelse av eiendomsselskap med tilhørende utvikling og drift av næringseiendommer. Investering i aksjer samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −66,000
▲ +43 %
Equity
NOK 16.4m
▼ −3 %
Est. value
NOK 14.9m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
90.1%
Very good
Equity as a share of total capital

Who owns BJØRNØYGATEN AS?

BJØRNØYGATEN AS
· NOK −66,000 profit

BJØRNØYGATEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRNØYGATEN AS own?

BJØRNØYGATEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BJØRNØYGATEN AS

Who owns BJØRNØYGATEN AS?

Kenneth Emil Jekteberg is the largest registered owner, with 100.0%.

Who is the general manager of BJØRNØYGATEN AS?

Kenneth Emil Jekteberg is registered as general manager of BJØRNØYGATEN AS.

Where is BJØRNØYGATEN AS based?

BJØRNØYGATEN 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 03.10.2026.

Report a problem

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