BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

STUDENTKORTET.NO AS

Org. no. 989909754 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 1.7m
Equity NOK 2.0m
Incorporated 2006
Share capital NOK 403,000

STUDENTKORTET.NO AS is registered as a limited company in Bergen, Vestland with organisation number 989909754. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 2006. Registered share capital is NOK 403,000, divided into 4032356 shares. The company's stated purpose is: “Etablere og selge studentkort for studenter og i den forbindelse knytte avtaler og rettigheter til bruk av kortet som er gode og rimelige for innehaveren av kortet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 1.7m
Equity
NOK 2.0m
Est. value
NOK 6.4m

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.2%
Good
Equity as a share of total capital

Who owns STUDENTKORTET.NO AS?

BEJOMA HOLDING AS
STUDENTKORTET.NO AS
NOK 7.4m rev. · NOK 1.7m profit

STUDENTKORTET.NO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STUDENTKORTET.NO AS

Who owns STUDENTKORTET.NO AS?

BEJOMA HOLDING AS is the largest registered owner, with 96.8%.

What is the revenue of STUDENTKORTET.NO AS?

STUDENTKORTET.NO AS had revenue of NOK 7.4m in 2024.

Who is the general manager of STUDENTKORTET.NO AS?

Joachim Kittang Gjesdal is registered as general manager of STUDENTKORTET.NO AS.

Where is STUDENTKORTET.NO AS based?

STUDENTKORTET.NO 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.