BIZTRAC BETA
Rental and operating of own or leased real estate

SFP HOLDING AS

Org. no. 999020100 Limited company (AS) Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 124,000
Operating profit NOK 44,000
Equity NOK 7.6m
Incorporated 2012
Share capital NOK 1.2m

SFP HOLDING AS is registered as a limited company in Hå, Rogaland with organisation number 999020100. 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 1.2m, divided into 1200000 shares. The company's stated purpose is: “Aksjeinvesteringer, kjøp, salg og utleie av eiendom, kjøp og salg av verdipapirer, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 124,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 124,000
Operating profit
NOK 44,000
Equity
NOK 7.6m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns SFP HOLDING AS?

T. FIGVED INVEST AS
SFP HOLDING AS
NOK 124,000 rev. · NOK 44,000 profit

SFP HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SFP HOLDING AS own?

SFP HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about SFP HOLDING AS

Who owns SFP HOLDING AS?

T. FIGVED INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of SFP HOLDING AS?

SFP HOLDING AS had revenue of NOK 124,000 in 2024.

Who is the general manager of SFP HOLDING AS?

Tommy Figved is registered as general manager of SFP HOLDING AS.

Where is SFP HOLDING AS based?

SFP HOLDING AS has its business address in Nærbø.

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.