biztrac. BETA
COMPANY REGISTER PROFILE
995899639 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BJELKEBUKT AS

Org. no. 995899639 Limited company (AS) Bærum Incorporated 2010 Active
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 813,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

BJELKEBUKT AS is registered as a limited company in Bærum, Akershus with organisation number 995899639. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i ulike rådgivende virksomheter, verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
▼ −95 %
Equity
NOK 813,000
▲ +2 %
Est. value
NOK 510,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
1.5%
Weak
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BJELKEBUKT AS?

BJELKEBUKT AS
NOK 0 rev. · NOK −23,000 profit

BJELKEBUKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJELKEBUKT AS own?

BJELKEBUKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJELKEBUKT AS

Who owns BJELKEBUKT AS?

Rolf Ole Jensen is the largest registered owner, with 100.0%.

What is the revenue of BJELKEBUKT AS?

BJELKEBUKT AS had revenue of NOK 0 in 2025.

Who is the general manager of BJELKEBUKT AS?

Rolf Ole Jensen is registered as general manager of BJELKEBUKT AS.

Where is BJELKEBUKT AS based?

BJELKEBUKT AS has its business address in Rykkinn.

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.