BIZTRAC BETA
Rental and operating of own or leased real estate

JABRA INVEST AS

Org. no. 989014935 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 755,000
Operating profit NOK 719,000
Equity NOK 6.5m
Incorporated 2005
Share capital NOK 100,000

JABRA INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 989014935. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kapitalforvaltning ved investering i finansielle instrumenter og fast eigedom, samt å levere konsulentbistand.”. The most recent filed accounts, for the 2024 financial year, show NOK 755,000 in revenue and NOK 719,000 in operating profit.

Key figures · 2024

Revenue
NOK 755,000
Operating profit
NOK 719,000
Equity
NOK 6.5m
Est. value
NOK 6.1m

Financial health · 2024

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
61.0%
Very good
Equity as a share of total capital

Who owns JABRA INVEST AS?

JAN BRANÆS
JABRA INVEST AS
NOK 755,000 rev. · NOK 719,000 profit

JABRA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JABRA INVEST AS own?

JABRA INVEST AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about JABRA INVEST AS

Who owns JABRA INVEST AS?

JAN BRANÆS is the largest registered owner, with 100.0%.

What is the revenue of JABRA INVEST AS?

JABRA INVEST AS had revenue of NOK 755,000 in 2024.

Who is the general manager of JABRA INVEST AS?

Jan Branæs is registered as general manager of JABRA INVEST AS.

Where is JABRA INVEST AS based?

JABRA INVEST AS has its business address in Stabekk.

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.