BIZTRAC BETA
Other captive investment companies

BEJIMAR AS

Org. no. 926035282 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK −78,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−78k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

BEJIMAR AS is registered as a limited company in Bergen, Vestland with organisation number 926035282. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer, og andre verdipapirer, aktiviteter relatert til oppdrett av fisk samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK −78,000

Financial health · 2025

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

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

Who owns BEJIMAR AS?

2048 RELAX AS
BEJIMAR AS
NOK 0 rev. · NOK −29,000 profit

BEJIMAR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEJIMAR AS

Who owns BEJIMAR AS?

2048 RELAX AS is the largest registered owner, with 40.0%.

What is the revenue of BEJIMAR AS?

BEJIMAR AS had revenue of NOK 0 in 2025.

Who is the general manager of BEJIMAR AS?

Marius Arnesen is registered as general manager of BEJIMAR AS.

Where is BEJIMAR AS based?

BEJIMAR AS has its business address in Bergen.

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.