BIZTRAC BETA
Uoppgitt

BJØRNEBY INVEST AS

Org. no. 827727202 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 31,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

BJØRNEBY INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 827727202. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i oppstartselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 31,000
Est. value
NOK 36,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJØRNEBY INVEST AS?

ANDERS BJØRNEBY
BJØRNEBY INVEST AS
NOK 0 rev. · NOK −2,000 profit

BJØRNEBY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRNEBY INVEST AS own?

BJØRNEBY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRNEBY INVEST AS

Who owns BJØRNEBY INVEST AS?

ANDERS BJØRNEBY is the largest registered owner, with 100.0%.

What is the revenue of BJØRNEBY INVEST AS?

BJØRNEBY INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of BJØRNEBY INVEST AS?

Anders Bjørneby is registered as general manager of BJØRNEBY INVEST AS.

Where is BJØRNEBY INVEST AS based?

BJØRNEBY INVEST AS has its business address in Oslo.

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.