Jump to content

Talk:Defqon.1 Festival

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

References

[edit]

Are there any references for the number of visitors and number of performers? I just added two sources and had to correct one value but I am not sure whether the other numbers are correct... 130.75.130.194 (talk) — Preceding undated comment added 21:58, 7 July 2014 (UTC)[reply]

Orgin of the name

[edit]

Hey everyone, I was thinking, is it true that the name Defqon.1 was made out of the names 'D-Block & S-te-Fan' and 'Q-Dance'?

Like: D = from D-block E = from st-E-fan F = from st-e-Fan Q = from Q-dance O = from d-blOck N = from st-e-faN

Let me know if this is true, so we can add it!

- GalaxyDeem GalaxyDeem (talk) 14:39, 8 September 2020 (UTC)[reply]

This is almost certainly not true, Defqon.1's first edition was held in 2003 while Discogs (https://www.discogs.com/artist/550090-D-Block-S-te-fan) states that D-Block & S-te-Fan's first track "Fresh New Beat" was released in 2005. I think that it is fairly safe to say that Q-Dance would not be able to name their festival after a producer duo that had not released music when the first named edition took place. Additionally, I think it is logical to say that naming a festival after a single artist is quite risky (aside from special events such as X-Qlusive Artist Name Here, which are one-off events), especially if that artist has not released music yet.
In reality, I think it is exceedingly likely that Defqon.1 is named after DEFCON 1 from the DEFCON rating system, with the 'Q' replacing the 'C' as it does for most other Q-dance events (e.g. Qlimax). CuddlyKoala43 (talk) 04:33, 16 July 2022 (UTC)[reply]

A Commons file used on this page or its Wikidata item has been nominated for deletion

[edit]

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 07:06, 29 June 2022 (UTC)[reply]