BIZTRAC BETA
Rental and operating of own or leased real estate

FRYDENLUND HANDELSEIENDOM NARVIK AS

Org. no. 997415914 Limited company (AS) Ringerike Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1.8m
Equity NOK 4.0m
Incorporated 2011
Share capital NOK 2.1m

Signals

1 flags
  • Nylig endring 2026-07-10 Adresseendring registrert 2026-07-10.

FRYDENLUND HANDELSEIENDOM NARVIK AS is registered as a limited company in Ringerike, Buskerud with organisation number 997415914. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 2.1m, divided into 100 shares. The company's stated purpose is: “Eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1.8m
Equity
NOK 4.0m
Est. value
NOK 5.0m

Financial health · 2024

Liquidity
2.42
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.1%
Satisfactory
Equity as a share of total capital

Who owns FRYDENLUND HANDELSEIENDOM NARVIK AS?

AKA AS
FRYDENLUND HANDELSEIENDOM NARVIK AS
NOK 3.0m rev. · NOK 1.8m profit

FRYDENLUND HANDELSEIENDOM NARVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRYDENLUND HANDELSEIENDOM NARVIK AS

Who owns FRYDENLUND HANDELSEIENDOM NARVIK AS?

AKA AS is the largest registered owner, with 100.0%.

What is the revenue of FRYDENLUND HANDELSEIENDOM NARVIK AS?

FRYDENLUND HANDELSEIENDOM NARVIK AS had revenue of NOK 3.0m in 2024.

Where is FRYDENLUND HANDELSEIENDOM NARVIK AS based?

FRYDENLUND HANDELSEIENDOM NARVIK AS has its business address in Hønefoss.

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.