BIZTRAC BETA
Buying and selling of own real estate

FLOKE HOLDING AS

Org. no. 924353031 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 8,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

FLOKE HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 924353031. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 8,000
Est. value
NOK 7,000

Financial health · 2025

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

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

Who owns FLOKE HOLDING AS?

GUNNAR RØRVIK
FLOKE HOLDING AS
· NOK −11,000 profit

FLOKE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLOKE HOLDING AS own?

FLOKE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLOKE HOLDING AS

Who owns FLOKE HOLDING AS?

GUNNAR RØRVIK is the largest registered owner, with 100.0%.

Who is the general manager of FLOKE HOLDING AS?

Gunnar Rørvik is registered as general manager of FLOKE HOLDING AS.

Where is FLOKE HOLDING AS based?

FLOKE HOLDING AS has its business address in Stavanger.

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.