BIZTRAC BETA
Buying and selling of own real estate

FRYDENSBORGVEIEN 1 KRAGERØ AS

Org. no. 928157067 Limited company (AS) Kragerø Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 675,000
Operating profit NOK 367,000
Equity NOK 497,000
Incorporated 2021
Share capital NOK 30,000

FRYDENSBORGVEIEN 1 KRAGERØ AS is registered as a limited company in Kragerø, Telemark with organisation number 928157067. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 574 shares. The company's stated purpose is: “Investere i finans- og realobjekter samt utleie av disse.”. The most recent filed accounts, for the 2025 financial year, show NOK 675,000 in revenue and NOK 367,000 in operating profit.

Key figures · 2025

Revenue
NOK 675,000
Operating profit
NOK 367,000
Equity
NOK 497,000
Est. value
NOK 671,000

Financial health · 2025

Liquidity
2.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns FRYDENSBORGVEIEN 1 KRAGERØ AS?

JAHEKA HOLDING AS
FRYDENSBORGVEIEN 1 KRAGERØ AS
NOK 675,000 rev. · NOK 367,000 profit

FRYDENSBORGVEIEN 1 KRAGERØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRYDENSBORGVEIEN 1 KRAGERØ AS

Who owns FRYDENSBORGVEIEN 1 KRAGERØ AS?

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

What is the revenue of FRYDENSBORGVEIEN 1 KRAGERØ AS?

FRYDENSBORGVEIEN 1 KRAGERØ AS had revenue of NOK 675,000 in 2025.

Who is the general manager of FRYDENSBORGVEIEN 1 KRAGERØ AS?

Petter Carlsen is registered as general manager of FRYDENSBORGVEIEN 1 KRAGERØ AS.

Where is FRYDENSBORGVEIEN 1 KRAGERØ AS based?

FRYDENSBORGVEIEN 1 KRAGERØ AS has its business address in Kragerø.

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.