BIZTRAC BETA
Rental and operating of own or leased real estate

FRISK HOLDING AS

Org. no. 998212324 Limited company (AS) Sarpsborg Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 220,000
Operating profit NOK 99,000
Equity NOK 2.2m
Incorporated 2012
Share capital NOK 130,000

FRISK HOLDING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 998212324. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 130,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 220,000 in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 220,000
Operating profit
NOK 99,000
Equity
NOK 2.2m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns FRISK HOLDING AS?

PETER RAYMOND SUND
FRISK HOLDING AS
NOK 220,000 rev. · NOK 99,000 profit

FRISK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRISK HOLDING AS own?

FRISK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRISK HOLDING AS

Who owns FRISK HOLDING AS?

PETER RAYMOND SUND is the largest registered owner, with 100.0%.

What is the revenue of FRISK HOLDING AS?

FRISK HOLDING AS had revenue of NOK 220,000 in 2025.

Who is the general manager of FRISK HOLDING AS?

Peter Raymond Sund is registered as general manager of FRISK HOLDING AS.

Where is FRISK HOLDING AS based?

FRISK HOLDING AS has its business address in Skjeberg.

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.