biztrac. BETA
COMPANY REGISTER PROFILE
932749041 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

BEYKENT AS

Org. no. 932749041 Limited company (AS) Bergen Incorporated 2023 Active
Revenue 2025 NOK 18.1m
Operating profit NOK −206,000
Equity NOK −11,000
Incorporated 2023
Employees 8
Share capital NOK 500,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).

BEYKENT AS is registered as a limited company in Bergen, Vestland with organisation number 932749041. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Handel, investering i eiendommer, investering i aksjer og andeler, samt andre finansplasseringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.1m in revenue and NOK −206,000 in operating profit.

Key figures · 2025

Revenue
NOK 18.1m
▲ +10 %
Operating profit
NOK −206,000
▼ −53 %
Equity
NOK −11,000
▼ −103 %

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
-6.7%
Not satisfactory
Return on total assets
Solidity
-0.4%
Weak
Equity as a share of total capital

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

Who owns BEYKENT AS?

BEYKENT AS
NOK 18.1m rev. · NOK −206,000 profit

BEYKENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEYKENT AS

Who owns BEYKENT AS?

AKGEYIK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BEYKENT AS?

BEYKENT AS had revenue of NOK 18.1m in 2025.

Where is BEYKENT AS based?

BEYKENT 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 03.10.2026.

Report a problem

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