BIZTRAC BETA
FLYING CULINARY CIRCUS AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Leasing of intellectual property and similar products, except copyrighted works

FLYING CULINARY CIRCUS AS

Org. no. 998574587 Limited company (AS) Oslo Incorporated 2012 Bankrupt
Ownership graph ↗
Incorporated 2012
Employees 5
Share capital NOK 100,000

Signals

2 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Nylig endring 2026-05-21 Konkurs registrert 2026-05-21.

FLYING CULINARY CIRCUS AS is registered as a limited company in Oslo, Oslo with organisation number 998574587. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å eie og drive merkevaren "The Flying Culinary Circus", samt besitte rettighetene til navnet. Videre skal selskapet drive med salg og utvikling av egne produkter, tv-produksjoner, cateringsoppdrag, event- og reiselivsvirksomhet, samt inneha rettigheter til andre prosjekter som naturlig hører inn under dette. Selskapet skal kunne delta i andre selskaper gjennom erverve aksjer eller på annen måte besitte eierandeler.”.

Who owns FLYING CULINARY CIRCUS AS?

SVENDGÅRD INVEST AS
FLYING CULINARY CIRCUS AS

FLYING CULINARY CIRCUS AS has 5 registered shareholders:

All shareholders and roles →

Which companies does FLYING CULINARY CIRCUS AS own?

FLYING CULINARY CIRCUS AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FLYING CULINARY CIRCUS AS

Who owns FLYING CULINARY CIRCUS AS?

SVENDGÅRD INVEST AS is the largest registered owner, with 20.0%.

Where is FLYING CULINARY CIRCUS AS based?

FLYING CULINARY CIRCUS AS has its business address in Oslo.

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.