biztrac. BETA
COMPANY REGISTER PROFILE
833254022 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other education activities

POLARJENTER AS

Org. no. 833254022 Limited company (AS) Hjelmeland Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 23,000
Operating profit NOK 7,000
Equity NOK 49,000
Incorporated 2024
Share capital NOK 50,000

POLARJENTER AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 833254022. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Formidling av egne og andres turer og opplevelser. Historisk, nåtid og framtid. Samt arrangere turer og arrangementer i tillegg til salg av varer og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
Operating profit
NOK 7,000
▲ +190 %
Equity
NOK 49,000
▲ +16 %
Est. value
NOK 47,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns POLARJENTER AS?

POLARJENTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about POLARJENTER AS

Who owns POLARJENTER AS?

Karen Malena Kyllesø is the largest registered owner, with 40.0%.

What is the revenue of POLARJENTER AS?

POLARJENTER AS had revenue of NOK 23,000 in 2025.

Who is the general manager of POLARJENTER AS?

Karen Malena Kyllesø is registered as general manager of POLARJENTER AS.

Where is POLARJENTER AS based?

POLARJENTER AS has its business address in Årdal I Ryfylke.

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.