BIZTRAC BETA
COMPANY REGISTER PROFILE
992115025 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

BARE EB INVEST AS

Org. no. 992115025 Limited company (AS) Gjerdrum Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −48,000
Equity NOK 4.0m
Incorporated 2007
Share capital NOK 100,000

Signals

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

BARE EB INVEST AS is registered as a limited company in Gjerdrum, Akershus with organisation number 992115025. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “KJØPE OG SELGE VERDIPAPIRER SAMT DELTA I ANDRE SELSKAPER.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −48,000
▲ +1 %
Equity
NOK 4.0m
▼ −1 %
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns BARE EB INVEST AS?

BARE EB INVEST AS
NOK 0 rev. · NOK −48,000 profit

BARE EB INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BARE EB INVEST AS own?

BARE EB INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BARE EB INVEST AS

Who owns BARE EB INVEST AS?

EGIL TANDBERG BRÅTHEN is the largest registered owner, with 100.0%.

What is the revenue of BARE EB INVEST AS?

BARE EB INVEST AS had revenue of NOK 0 in 2025.

Where is BARE EB INVEST AS based?

BARE EB INVEST AS has its business address in Gjerdrum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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