Tyrus (wrestler)

# Tyrus (wrestler)

## Abstract

George Murdoch (born February 21, 1973) is an American cable news personality, actor, and former professional wrestler known by his ring/stage name Tyrus. As a wrestler, he was formerly signed to the National Wrestling Alliance (NWA), where he is a former NWA Worlds Heavyweight Champion. As a cable news personality, he appears on Fox News, and its sister streaming service Fox Nation, primarily as a co-host/panelist on the late-night talk show Gutfeld!, as well as a contributor/fill-in host on other programs. In 2024, Tyrus was named host of Maintaining with Tyrus on the streaming platform OutKick, which is owned by Fox.

After training in WWE's developmental territories, such as Deep South Wrestling (DSW) and Florida Championship Wrestling (FCW), Murdoch under the ring name Brodus Clay debuted during the fourth season of NXT, a WWE television show where rookies were paired with established WWE wrestlers as mentors. He debuted on the main roster as Alberto Del Rio 's bodyguard. During 2012, WWE changed his gimmick to The Funkusaurus, a funk dancer accompanied by his backup dancers the Funkadactyls. He wrestled in WWE until his departure in 2014. From 2014 to 2017, Murdoch wrestled in Total Nonstop Action Wrestling (TNA) under the ring name of Tyrus. In 2021, he joined the NWA, where he won the NWA World Television Championship, and later the promotion's primary title — the Worlds Heavyweight Championship.

His 2022 autobiography Just Tyrus: A Memoir was a New York Times bestseller. His second book Nuff Said was released in 2023.

## Early life

Murdoch is biracial; his father is black and his mother is white. He has stated that when he was born, his father was 19 years old and his mother was 15. In 2018, Murdoch disclosed a childhood incident in which his abusive father damaged his eye by hitting him; this incident led his mother to leave his father. While Murdoch's mother moved back to her parents' home, Murdoch has stated that he and his brother were not welcome there because they were part black. According to Murdoch, he and his brother lived with a foster family for many years; during this time, Murdoch was "obsessed" with changing his skin color, thinking that this would allow him to be reunited with his family. Murdoch and his brother eventually lived with their mother again, but Murdoch left home at age 15.

In 1990, Murdoch attended Quartz Hill High School in Los Angeles County, California, and then in 1992, Antelope Valley College in Lancaster. By 1995, he was attending the University of Nebraska at Kearney, where he studied to become a teacher, and played college football for the Lopers. However, Murdoch has stated that his football career ended when surgery to remove a ruptured appendix severed nerve endings in his leg, leaving him with a permanent limp.

Murdoch has worked as a bodyguard for Snoop Dogg.

Murdoch married to his longtime girlfriend Ingrid on January 6,2024. (https://clerk.clarkcountynv.gov/AcclaimWeb/Marriage/FindMyMarriageRecordSearch)

## Professional wrestling career

### World Wrestling Entertainment / WWE

#### Developmental territories (2006–2008)

After signing a contract with World Wrestling Entertainment (WWE), Murdoch was assigned to Deep South Wrestling (DSW), a WWE developmental territory, where he worked as G-Rilla, adopting the gimmick of a street thug. He worked in DSW until June 2007, when he was assigned to Florida Championship Wrestling, other WWE develomental territory. Murdoch worked in FCW, wrestling for the FCW Southern Heavyweight Championship against Harry Smith on September 25, but lost via disqualification, but he was released from his contract on February 4, 2008.

#### NXT and alliance with Alberto Del Rio (2010–2011)

After a two year hiatus, in January 2010, Murdoch re-signed with WWE and returned to FCW. While he started with the G-Rilla ringname, he began to use the name of Brodus Clay, a play on Snoop Dogg's real name (Calvin Cordozar Broadus), in May 2010. During the finale of season three of NXT, Clay was named part of the fourth season, with Ted DiBiase and Maryse as his Pros. He made his in-ring debut on NXT on the December 14, 2010, episode, teaming with DiBiase to defeat Byron Saxton and his mentor Chris Masters. During the season, he won a four-way elimination match on the January 25 episode of NXT, earning the right to choose a new Pro, picking Alberto Del Rio. In the season finale, Clay ended the competition in second place, losing to Curtis.

Following his stint in NXT, on the March 7 episode of Raw, Clay debuted as Del Rio's new bodyguard. As Del Rio was feuding with Edge and Christian, Clay faced off with single matches against them and also teamed with Del Rio to face Edge and Christian. Clay accompanied Del Rio to the ring at WrestleMania XXVII for his match with Edge. On the April 25 episode of Raw, Del Rio was drafted to Raw, while Clay remained on SmackDown. Clay's final appearance with Del Rio occurred on May 1 at Extreme Rules, when he interfered on Del Rio's behalf as Del Rio faced Christian in a ladder match for the vacant World Heavyweight Championship. Despite this, Del Rio was unsuccessful in winning the match. After a three-month absence due to the filming of the movie No One Lives, Clay reappeared on the August 4, 2011, episode of Superstars, where he defeated Pat Silva. Over the next few weeks, Clay continued to squash various jobbers on Superstars.

#### The Funkasaurus (2012–2014)

WWE ran vignettes promoting his return to television on the November 7, 2011, episode of Raw. However, Clay's television return was continuously delayed by authority figure John Laurinaitis to be "next week", with this trend continuing all the way into January 2012. Around this time, Clay was informed by management that he would be portraying a dancing face character upon his return. He was hesitant to follow through with their request, but gained the confidence to try it with encouragement from Dusty Rhodes. Clay made his television return on the January 9, 2012, episode of Raw as a face (heroic character) with a fun-loving, funk dancing gimmick, with the nickname "The Funkasaurus" and began using Ernest "The Cat" Miller 's theme song "Somebody Call My Momma". Now accompanied by The Funkadactyls (Naomi and Cameron) and announced as hailing from "Planet Funk", Clay incorporated gyrations and dance moves into his various squash wins on both Raw and SmackDown. Clay made his pay-per-view singles debut at the Royal Rumble on January 29, quickly defeating Drew McIntyre.

At WrestleMania XXVIII, Clay made an on-stage appearance, calling and dancing with Momma Clay. The following night on Raw, Clay started a feud with Dolph Ziggler and Jack Swagger when he saved Santino Marella from them. Clay and Marella beat Ziggler and Swagger on the April 9 episode of Raw. On the April 20 episode of SmackDown, Clay began a brief association with Hornswoggle. At Extreme Rules, Clay defeated Ziggler. By May, Clay was on a 21-match winning streak since adopting the Funkasaurus gimmick.

On the May 28 episode of Raw, Big Show justified his recent heel turn by blaming Clay. Hearing this, Clay then challenged Big Show to a match that night. Before the match could start, Big Show attacked Clay at ringside and brutally assaulted him. On the June 8 episode of SmackDown, Clay was banned by General Manager John Laurinaitis from appearing on Raw "to protect him from Big Show" so he was transferred to SmackDown. Big Show's attack also led Clay to vow to be more aggressive in the ring. At No Way Out, Clay defeated David Otunga in the pre-show match. Later during the pay-per-view, Clay interfered in the main event steel cage match, costing Big Show the match to John Cena and as per the match stipulation, causing the firing of John Laurinaitis. Big Show then made an appearance on the June 22 episode of SmackDown, leading to Clay physically confronting him. With Laurinaitis fired, Clay was allowed to return to Raw from June 25, where he faced Big Show; Big Show defeated Clay to end Clay's 24-match winning streak. Clay then began a feud with Damien Sandow on the July 30 episode of Raw; Sandow attacked Clay when he laughed at a video of Sandow's beatdown at the hands of DX. Clay and Sandow finally faced off on the August 20 episode of Raw, where Sandow won, but he was attacked by Clay after the match. At the Survivor Series pay-per-view, Clay took part in 10 man elimination tag team match alongside Tyson Kidd, Justin Gabriel, Rey Mysterio and Sin Cara, but he was the first man out after being eliminated by Tensai.

In January 2013, Clay competed in the 2013 Royal Rumble match and was eliminated by five men. Tensai was embarrassed after a dance contest, but Clay encouraged him to dance and have fun because "what happens in Vegas stays in Vegas". Tensai, with Clay's encouragement, began using several "silly dance moves". Two days later on WWE Main Event, Clay came out to support Tensai during his match with Titus O'Neil. Following this, Clay and Tensai formed a tag team and went on to defeat established teams such as Primo & Epico, Heath Slater and Jinder Mahal of 3MB and Team Rhodes Scholars (Cody Rhodes and Damien Sandow). On the March 22 episode of SmackDown, Tensai and Clay were defeated by Team Rhodes Scholars after an interference from The Bella Twins. Tensai and Clay announced their official tag-team name "Tons of Funk" on the March 27 episode of Main Event, where they accompanied The Funkadactyls to ring in a losing effort to The Bella Twins. The two teams were originally booked to face each other in an eight-person mixed tag team match on April 7 at WrestleMania 29, but their match was cut due to time constraints. The match instead took place the following night on Raw, where Tons of Funk and The Funkadactyls emerged victorious.

In November 2013, Clay started a storyline where he became angry and jealous of the debuting Xavier Woods, who "borrowed" Clay's music and The Funkadactyls for his entrance. Clay thus began to exhibit more villainous tendencies, such as repeatedly attacking Woods, after he had defeated Woods in a match. At TLC: Tables, Ladders & Chairs, Clay faced Woods' partner, R-Truth and continually assaulted Truth instead of going for a win, so Tensai and the Funkadactyls left in protest and Clay lost the match.

On the next day on Raw, Clay completed his heel turn by abandoning Tensai to lose their tag match and attacking Tensai after the match. Clay found no immediate success, as he went on to lose to Tensai, Woods and Truth in singles matches. On the April 17 episode NXT, Clay would lose by countout against Adrian Neville in a non-title match. His final match was he lost to Adrian Neville for the NXT Champion in no disqualification match. On June 12, 2014, Clay was released by WWE.

### Total Nonstop Action Wrestling / Impact Wrestling (2014–2018)

On September 16, 2014, Murdoch debuted for Total Nonstop Action Wrestling (TNA) under the ring name Tyrus at TNA's television tapings, aligning himself with Ethan Carter III (EC3). Moments after EC3 introduced him, he had his first wrestling match on the October 15 episode of Impact Wrestling against Shark Boy, which he won. Together they entered the TNA World Tag Team Championship number one contenders tournament, defeating Eric Young and Rockstar Spud in the quarterfinals, only to lose to The Hardy Boyz on the October 29 episode of Impact Wrestling in the semifinals, when Tyrus was pinned by Matt Hardy. At Lockdown, Tyrus defeated Spud and Mark Andrews in a 2-on-1 Six Sides of Steel match. At Joker's Wild 2015, Tyrus and Knux lost to Ethan Carter III and Crazzy Steve. At Hardcore Justice 2015. Tyrus competed in a 12-man Hardcore Gauntlet Battle Royal which was won by James Storm. On May 15, 2015, episode of Impact Wrestling, Tyrus lost to Mr. Anderson. At Slammiversary, Carter and Tyrus defeated Lashley and Mr. Anderson in the co-main event. At World Cup 2015, Tyrus (representing Team EC3) defeated Team Hardy's Gunner and later in the main event Team Hardy defeated Team EC3 in a Six-on-Six Elimination Tag Team match failing to win the world cup. At Turning Point, Tyrus lost to Matt Hardy.

On October 4, 2015, at Bound For Glory, Tyrus won a gauntlet for the gold match to become the number one contender for the TNA World Heavyweight Championship. On April 26, 2016 at Sacrifice (2016) Tyrus would get his championship match but lost to Drew Galloway.

At One Night Only: Live!, Tyrus lost to Lashley. At Joker's Wild 2016, Tyrus and Jade defeated Lashley and Gail Kim to qualify for the Gauntlet Battle Royal match later that night where Drew Galloway won the 14-person intergender Joker's Wild gauntlet battle royal. On a June 28, 2016, taping of Impact Wrestling, Tyrus returned as a "fixer" for hire, siding with Grado and Mahabali Shera in a match against The Tribunal and Al Snow. Since then, TNA began airing vignettes for the "fixer" gimmick on Impact Wrestling on weekly basis. At One Night Only: September 2016, Tyrus defeated Crazzy Steve. This was his first singles victory since Bound for Glory. At Against All Odds (aired November 4, 2016), Tyrus defeated Trevor Lee. At Bound for Glory, Tyrus competed in a 10-Man Bound for Gold Gauntlet match which was won by Eli Drake.

Tyrus returned to Impact Wrestling and began aligning himself with Eli Drake. At Joker's Wild 2017, Tyrus and Crazzy Steve lost to Mike Bennett and Braxton Sutter. On January 6, 2017, Tyrus and Eli Drake unsuccessfully challenged The Broken Hardys (Jeff Hardy and Matt Hardy) for the TNA World Tag Team Championships at TNA One Night Only: Live!. On August 18, 2017, the promotion announced that Tyrus was granted his release from his contract. Murdoch explained that he didn't feel comfortable with Jeff Jarrett returning to Impact, since Murdoch decided in the past to stay with TNA and didn't sign a contract with GFW.

At Impact's January 2018 tapings, he returned to defeat his former boss Ethan Carter III after turning on him. However, his return was short-lived when, on April 18, 2018, Tyrus left Impact once again, confirming his release and departure from the company. Murdoch claimed that poor booking decisions involving his character would hurt his reputation, so he left the promotion again.

### Independent circuit (2018)

Tyrus made his debut for Tommy Dreamer 's House of Hardcore at House of Hardcore 52 on December 8, teaming with Robert Strauss to unsuccessfully face David Arquette and RJ City.

### National Wrestling Alliance (2021–2023)

On March 11, 2021, National Wrestling Alliance announced on their social media that Tyrus would make his NWA debut at Back For The Attack defeating Kratos. On the April 20 episode of NWA Powerrr, Tyrus defeated Marshe Rockett and Matt Cross to become number one contender for the NWA World Television Championship. The next week, Tyrus and The Pope fought to a 6-minute time limit draw for the NWA Television Championship. On June 6 at When Our Shadows Fall, Tyrus defeated The Pope in a non-title match. On the August 6 episode of Powerrr, Tyrus defeated The Pope to win the NWA World Television Championship. Tyrus successfully defended his title in his first title defense against BLK Jeez. During his reign, Tyrus successfully defended the NWA World Television Championship against various contenders, such as Jordan Clearwater, Cyon, Jaden Roller, Rodney Mack, Mims and Odinson.

Tyrus unsuccessfully challenged Trevor Murdoch for the NWA Worlds Heavyweight Championship at NWA 74th Anniversary Show on August 28, 2022. On the September 24, 2022, episode of NWA USA, Tyrus vacated the NWA World Television Championship using the "Lucky 7" rule to challenge Murdoch and Matt Cardona for the NWA Worlds Heavyweight Championship at NWA Hard Times 3. At the event on November 12, Tyrus pinned Murdoch to win the title, marking his first world championship in his career.

On February 11, 2023, at Nuff Said, Tyrus successfully defended his title in his first title defense against Matt Cardona, with the help from Bully Ray, whom he promised to give a title shot anytime he wanted afterwards. Tyrus, holding the NWA Worlds Heavyweight Championship belt, was featured in a commercial for Fox News Channel's talk show 'Gutfeld!' during Super Bowl LVII. On April 7 at NWA 312, Tyrus successfully defended the NWA Worlds Heavyweight Championship against Chris Adonis. On June 3, during night one of the Crockett Cup, Tyrus teamed with Adonis under the name "The Midnight Riders" to compete in the namesake tournament, defeating The Warriors from the Wasteland (Judais and Max the Impaler) in the second round, and The Immortals (Kratos and Odinson) in the quarterfinal but lost to Knox and Murdoch (Mike Knox and Trevor Murdoch) in the semifinal. On the July 11 episode of Powerrr, after EC3 successfully defended the NWA National Heavyweight Championship, he dropped the title in the ring, officially relinquishing it to challenge Tyrus for the NWA Worlds Heavyweight Championship at NWA 75th Anniversary Show (NWA 75). Over two weeks later, Tyrus requested that the match be made a bullrope match given the history between him and EC3 stemming across Impact Wrestling and WWE. He also proposed the stipulation that he would retire should he lose the match. On August 27, at NWA 75, Tyrus lost the NWA World title Bullrope match to EC3, thus he was forced to retire. After the match, he said his good byes and thanked his family, the NWA and Billy Corgan; and the NWA locker room came out to embrace Tyrus.

## Television commentary career

In November 2016, Fox News host Greg Gutfeld invited Murdoch to appear as a guest commentator on The Greg Gutfeld Show; after Murdoch's first appearance, Gutfeld offered to have him back on the show – using his stage name "Tyrus" – twice a month. He then began making guest appearances on various programs on Fox News Channel, including The Five. Gutfeld has jokingly referred to Tyrus as his "massive sidekick." Subsequently, he became a regular contributor on Fox News host Dana Perino ’s former daytime news show, The Daily Briefing. Since April 2021, Tyrus has been a regular panelist on Gutfeld's relaunched 10 p.m. show, Gutfeld!.

Though a supporter of former President Donald Trump, he did not vote in 2016 and it is unclear whether he did in the subsequent elections.

From 2018 to 2019, he was a co-host of the show Un-PC on Fox News's streaming channel, Fox Nation. In June 2019, he premiered a new Fox Nation show, Nuff Said.

In June 2023, Tyrus hosted the premiere episode of Fox News Saturday Night, where he served as an interim host throughout the year.

In 2024, Tyrus helmed a new series for the streaming platform OutKick entitled Maintaining with Tyrus, debuting on February 1.

### Sexual harassment allegation

In 2019, Un-PC co-host Britt McHenry accused Murdoch of sexual harassment after he allegedly sent her a series of lewd text messages. According to Fox News, the matter was investigated and resolved. However, on December 10, 2019, McHenry filed a sexual harassment suit against Fox News and Murdoch. Subsequently, McHenry claimed that she lost the phone containing text messages she says are central to her claims. In July 2021, she voluntarily dismissed the lawsuit and left the Fox network, apparently as part of a legal settlement.

## Filmography

## Championships and accomplishments

- National Wrestling Alliance NWA Worlds Heavyweight Championship (1 time) NWA World Television Championship (1 time)

- NWA Worlds Heavyweight Championship (1 time)

- NWA World Television Championship (1 time)

- Pennsylvania Premiere Wrestling PPW Heavyweight Championship (1 time)

- PPW Heavyweight Championship (1 time)

- Pro Wrestling Illustrated Ranked No. 58 of the top 500 singles wrestlers in the PWI 500 in 2023

- Ranked No. 58 of the top 500 singles wrestlers in the PWI 500 in 2023

- Total Nonstop Action Wrestling Bound for Gold (2015)

- Bound for Gold (2015)

- WWE Slammy Award (1 time) Best Dancer of the Year (2012)

- Slammy Award (1 time) Best Dancer of the Year (2012)

- Best Dancer of the Year (2012)

## Books

- Just Tyrus: A Memoir (2022), Post Hill Press

- Nuff Said (2023), Post Hill Press


Yelena Godina

# Yelena Godina

## Abstract

Yelena Mikhailovna Godina (Russian: Елена Михайловна Година) (born 17 September 1977) is a Russian former volleyball player, who was a member of the national team that won the gold medal at 2006 Volleyball World Championship in Japan and the silver medal at the 2000 Summer Olympics in Sydney. She also competed at the 1996 Summer Olympics in Atlanta and the 2008 Summer Olympics in Beijing.

## Honours

- 1998 World Championship – 3rd place

- 1999 World Cup – 2nd place

- 2000 Olympic Games – 2nd place

- 2002 World Championship – 3rd place

- 2006 World Championship – 1st place

- 2008 Olympic Games – 6th place

## Individual awards

- 1999 FIVB World Grand Prix "Best blocker"

- 2006 World Championship "Best server"


James Loye

# James Loye

## Abstract

James Loye (born 23 May 1979, Bristol, United Kingdom) is a British actor. He originated the part of Frodo Baggins in the Toronto and London production (Theatre Royal Drury Lane) of Lord of the Rings the Musical. He trained at The Royal Welsh College of Music and Drama. His theatre credits include Cymbeline and Twelfth Night at Regents Park Open Air Theatre for which he was nominated for the Ian Charlson award. He played Prince Charming in Rufus Norris' Sleeping Beauty at The Barbican, Young Vic and New Victory Theatre New York. His other credits include work at The Bristol Old Vic, Chichester Festival Theatre, Birmingham Rep, Salisbury Playhouse and The Sheffield Crucible.

He now lives in Montreal, Canada where he continues to work in theatre, television, film and the video games. Theatre includes Butcher, Robin Hood, Centaur Theatre, The Sound Of Music, NAC. His television credits includes The Art Of More (Season 1), Being Human, Ascension and Mohawk Girls. Film credits include X-Men Apocalypse and Francois Girard's film Hochelaga Land Of Souls (release 2017). He has appeared in Assassin's Creed Video games for Ubisoft and Eidos' Deus Ex.

For UK television, he has played Lieutenant David Mellis in the award-winning BBC series Dunkirk, and his radio credits include The White Guard, Who Shot Shelly?, Molière Imaginaire and King Lear.


Sarah Schmelzel

# Sarah Schmelzel

## Abstract

Sarah Hawley Schmelzel (born May 12, 1994) is an American professional golfer and LPGA Tour member.

## Early life, college and amateur career

Schmelzel grew up in Phoenix, Arizona. Although she started playing golf when she was five, Schmelzel first competed in gymnastics. She was a talented at uneven bars and was an Arizona State Champion in the discipline. In 2001, she watched Annika Sörenstam card a 59 at her home course of Moon Valley, which sparked a passion for the game.

Schmelzel was highly ranked in both the National Junior Golf Scoreboard rankings and the Golfweek junior rankings. She was a standout at Xavier Prep and won the 2011 Arizona State High School Championship. Schmelzel led her school to its third team state title in four years, and carded rounds of 71-66 at the state championship to tie the Arizona state high school record with Amanda Blumenherst. She won the AJGA Bass Pro Shops/Payne Stewart Championship by 12 strokes with rounds of 69-71-70.

Schmelzel attended the University of South Carolina between 2012 and 2016 and played on the South Carolina Gamecocks women's golf team, where she captured one individual title. She was on the Southeastern Conference All-Freshman Team and was an honorable mention All-American as a senior.

## Professional career

Schmelzel turned professional after graduating and joined the 2017 Symetra Tour. In her second season, she recorded seven top-10 finishes, including four top-five results in her last five events to finish 13th on the Epson Tour money list. She finished third at the inaugural LPGA Q-Series to earn her LPGA Tour card for the 2019 season.

In 2021, Schmelzel finished tied 17th at the Bank of Hope LPGA Match-Play, after her opponent Carlota Ciganda was assessed a slow-play penalty. Ciganda and Schmelzel came to the 18th hole tied, but as the slow-play penalty in match play is loss of hole, Schmelzel was awarded the hole, and won the match 1-up.

In 2022, Schmelzel made six birdies in her final seven holes to jump up the leaderboard into solo third at the LPGA Drive On Championship, her career-best finish on the LPGA Tour so far.

On March 10, 2024, she had her best finish, second-place at the Blue Bay LPGA tournament, with a 273 (−15) to first-time LPGA winner Bailey Tardy who shot a new tournament record 269 (−19). Schmelzel earned $208,128 to the winner's $330,000.

## Amateur wins

- 2005 Kingman City Junior Championship

- 2006 Mesa City Junior Championship, Yuma City Junior Championship, Tucson Conquistadores Spring Classic

- 2007 Yuma City Junior Championship, JGAA Winter Classic

- 2008 Antigua/Milt Coggins Arizona Junior Championship, Yuma City Junior Championship, Tucson Conquistadores Spring Classic, JGAA Fall Classic

- 2009 Yuma City Junior Championship, Thunderbird Invitational

- 2011 Arizona State High School Championship, Pro Shops/Payne Stewart Championship

- 2016 Bryan National Collegiate

Source:

## Results in LPGA majors

CUT = missed the half-way cut NT = no tournament T = tied

## LPGA Tour career summary

Official as of March 10, 2024 * Includes matchplay and other tournaments without a cut.

## World ranking

Position in Women's World Golf Rankings at the end of each calendar year.

^ As of March 11, 2024

## U.S. national team appearances

Professional

- Solheim Cup: 2024 (winners)


Igor Ivanović (Serbian footballer)

# Igor Ivanović (Serbian footballer)

## Abstract

Igor Ivanović (Serbian Cyrillic: Игор Ивановић; born 28 July 1997) is a Serbian professional footballer who plays as an attacking midfielder for Kazakhstani club Tobol.

## Career

Ivanović started out with his hometown club Jagodina, making his Serbian SuperLiga debut in August 2014, aged 17. He was transferred to Napredak Kruševac in August 2017.

On 30 March 2023, Ivanović signed for Astana.

On 25 July 2023, Tobol announced the signing of Ivanović on loan from Astana for the remainder of the 2023 season.


UTF-8

# UTF-8

## Abstract

UTF-8 is a character encoding standard used for electronic communication. Defined by the Unicode Standard, the name is derived from Unicode Transformation Format – 8-bit.

UTF-8 is capable of encoding all 1,112,064 (17 planes times 2 code points per plane, minus 2 technically-invalid surrogates) valid Unicode code points using a variable-width encoding of one to four one- byte (8-bit) code units. Code points with lower numerical values, which tend to occur more frequently, are encoded using fewer bytes. It was designed for backward compatibility with ASCII: the first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single byte with the same binary value as ASCII, so that a UTF-8-encoded document using only those characters is identical to the same text in ASCII and can be read by programs expecting such.

UTF-8 was designed as a superior alternative to UTF-1, a proposed variable-length encoding with partial ASCII compatibility which lacked some features including self-synchronization and fully ASCII-compatible handling of characters such as slashes. Ken Thompson and Rob Pike produced the first implementation for the Plan 9 operating system in September 1992. This led to its adoption by X/Open as its specification for FSS-UTF, which would first be officially presented at USENIX in January 1993 and subsequently adopted by the Internet Engineering Task Force (IETF) in RFC 2277 (BCP 18) for future internet standards work, replacing Single Byte Character Sets such as Latin-1 in older RFCs.

UTF-8 results in fewer internationalization issues than any alternative text encoding, and it has been implemented in all modern operating systems, including Microsoft Windows, and standards such as JSON, where, as is increasingly the case, it is the only allowed form of Unicode.

UTF-8 is the dominant encoding for the World Wide Web and other Internet technologies, accounting for 98.3% of all web pages, 99.1% of the top 100,000 pages, and up to 100% for many languages, as of 2024. Virtually all countries and languages have 95% or more use of UTF-8 encodings on the web.

## History

The International Organization for Standardization (ISO) set out to compose a universal multi-byte character set in 1989. The draft ISO 10646 standard contained a non-required annex called UTF-1 that provided a byte stream encoding of its 32-bit code points. This encoding was not satisfactory on performance grounds, among other problems, and the biggest problem was probably that it did not have a clear separation between ASCII and non-ASCII: new UTF-1 tools would be backward compatible with ASCII-encoded text, but UTF-1-encoded text could confuse existing code expecting ASCII (or extended ASCII), because it could contain continuation bytes in the range 0x21–0x7E that meant something else in ASCII, e.g., 0x2F for /, the Unix path directory separator.

In July 1992, the X/Open committee XoJIG was looking for a better encoding. Dave Prosser of Unix System Laboratories submitted a proposal for one that had faster implementation characteristics and introduced the improvement that 7-bit ASCII characters would only represent themselves; all multi-byte sequences would include only bytes where the high bit was set. The name File System Safe UCS Transformation Format (FSS-UTF) and most of the text of this proposal were later preserved in the final specification. In August 1992, this proposal was circulated by an IBM X/Open representative to interested parties. A modification by Ken Thompson of the Plan 9 operating system group at Bell Labs made it self-synchronizing, letting a reader start anywhere and immediately detect character boundaries, at the cost of being somewhat less bit-efficient than the previous proposal. It also abandoned the use of biases and instead added the rule that only the shortest possible encoding is allowed; the additional loss in compactness is relatively insignificant, but readers now have to look out for invalid encodings to avoid reliability and especially security issues. Thompson's design was outlined on September 2, 1992, on a placemat in a New Jersey diner with Rob Pike. In the following days, Pike and Thompson implemented it and updated Plan 9 to use it throughout, and then communicated their success back to X/Open, which accepted it as the specification for FSS-UTF.

UTF-8 was first officially presented at the USENIX conference in San Diego, from January 25 to 29, 1993. The Internet Engineering Task Force adopted UTF-8 in its Policy on Character Sets and Languages in RFC 2277 (BCP 18) for future internet standards work in January 1998, replacing Single Byte Character Sets such as Latin-1 in older RFCs.

In November 2003, UTF-8 was restricted by RFC 3629 to match the constraints of the UTF-16 character encoding: explicitly prohibiting code points corresponding to the high and low surrogate characters removed more than 3% of the three-byte sequences, and ending at U+10FFFF removed more than 48% of the four-byte sequences and all five- and six-byte sequences.

## Naming

The official name for the encoding is UTF-8, the spelling used in all Unicode Consortium documents. Most standards officially list it in upper case as well, but all that do are also case-insensitive and utf-8 is often used in code.

Some other spellings may also be accepted by standards, e.g. web standards (which include CSS, HTML, XML, and HTTP headers) explicitly allow utf8 (and disallow "unicode") and many aliases for encodings. Spellings with a space e.g. "UTF 8" should not be used. The official Internet Assigned Numbers Authority also lists csUTF8 as the only alias, which is rarely used.

In Windows, UTF-8 is codepage 65001 (i.e. CP_UTF8 in source code).

In MySQL, UTF-8 is called utf8mb4 (with utf8mb3, and its alias utf8, being a subset encoding for characters in the Basic Multilingual Plane).

In HP PCL, the Symbol-ID for UTF-8 is 18N.

In Oracle Database (since version 9.0), AL32UTF8 means UTF-8. Oracle previously used the UTF-8 name to refer to CESU-8, a deprecated variant.

UTF-8-BOM and UTF-8-NOBOM are sometimes used for text files which contain or do not contain a byte-order mark (BOM), respectively. In Japan especially, UTF-8 encoding without a BOM is sometimes called UTF-8N.

## Description

UTF-8 encodes code points in one to four bytes, depending on the value of the code point. In the following table, the x characters are replaced by the bits of the code point:

The first 128 code points (ASCII) need 1 byte. The next 1,920 code points need two bytes to encode, which covers the remainder of almost all Latin-script alphabets, and also IPA extensions, Greek, Cyrillic, Coptic, Armenian, Hebrew, Arabic, Syriac, Thaana and N'Ko alphabets, as well as Combining Diacritical Marks. Three bytes are needed for the remaining 61,440 codepoints of the Basic Multilingual Plane (BMP), including most Chinese, Japanese and Korean characters. Four bytes are needed for the 1,048,576 codepoints in the other planes of Unicode, which include emoji (pictographic symbols), less common CJK characters, various historic scripts, and mathematical symbols.

A whole graphic character can take more than 4 bytes, because it is made of more than one code point. For instance, a national flag character takes 8 bytes since it is "constructed from a pair of Unicode scalar values" both from outside the BMP. Some complex emoji characters can take even more than this: The transgender flag emoji (🏳⚧), which consists of the 5 code point sequence U+1F3F3 U+FE0F U+200D U+26A7 U+FE0F, requires sixteen bytes to encode, while that for the flag of Scotland (🏴) requires a total of 28 bytes for the 7 code point sequence U+1F3F4 U+E0067 U+E0062 U+E0073 U+E0063 U+E0074 U+E007F.

### Byte-order mark

If the Unicode byte-order mark (BOM, U+FEFF, technically the U+FEFF ZERO WIDTH NO-BREAK SPACE character) is at the start of a UTF-8 file, the first three bytes will be 0xEF, 0xBB, 0xBF.

The Unicode Standard neither requires nor recommends the use of the BOM for UTF-8, but warns that it may be encountered at the start of a file trans-coded from another encoding. While ASCII text encoded using UTF-8 is backward compatible with ASCII, this is not true when Unicode Standard recommendations are ignored and a BOM is added. A BOM can confuse software that isn't prepared for it but can otherwise accept UTF-8, e.g. programming languages that permit non-ASCII bytes in string literals but not at the start of the file. Nevertheless, there was and still is software that always inserts a BOM when writing UTF-8, and refuses to correctly interpret UTF-8 unless the first character is a BOM (or the file only contains ASCII).

### Invalid sequences and error handling

Not all sequences of bytes are valid UTF-8. A UTF-8 decoder should be prepared for:

- Bytes that can never appear in UTF-8: C0, C1, F5 – FF

- An unexpected continuation byte

- A non-continuation byte before the end of the character

- The string ending before the end of the character (which can happen in simple string truncation)

- An overlong encoding

- A sequence that decodes to an invalid code point

Many of the first UTF-8 decoders would decode these, ignoring incorrect bits and accepting overlong results. Carefully crafted invalid UTF-8 could make them either skip or create ASCII characters such as NUL, slash, or quotes. Invalid UTF-8 has been used to bypass security validations in high-profile products including Microsoft's IIS web server and Apache's Tomcat servlet container. RFC 3629 states "Implementations of the decoding algorithm MUST protect against decoding invalid sequences." The Unicode Standard requires decoders to: "... treat any ill-formed code unit sequence as an error condition. This guarantees that it will neither interpret nor emit an ill-formed code unit sequence."

Since RFC 3629 (November 2003), the high and low surrogate halves used by UTF-16 (U+D800 through U+DFFF) and code points not encodable by UTF-16 (those after U+10FFFF) are not legal Unicode values, and their UTF-8 encoding must be treated as an invalid byte sequence. Not decoding unpaired surrogate halves makes it impossible to store invalid UTF-16 (such as Windows filenames or UTF-16 that has been split between the surrogates) as UTF-8, while it is possible with WTF-8.

Some implementations of decoders throw exceptions on errors. This has the disadvantage that it can turn what would otherwise be harmless errors (such as a "no such file" error) into a denial of service. For instance early versions of Python 3.0 would exit immediately if the command line or environment variables contained invalid UTF-8.

Since Unicode 6 (October 2010), the standard (chapter 3) has recommended a "best practice" where the error is either one byte long, or ends before the first byte that is disallowed. In these decoders E1,A0,C0 is two errors (2 bytes in the first one). This means an error is no more than three bytes long and never contains the start of a valid character, and there are 21 952 different possible errors. The standard also recommends replacing each error with the replacement character "�" (U+FFFD).

These recommendations are not often followed. It is common to consider each byte to be an error, in which case E1,A0,C0 is three errors (each 1 byte long). This means there are only 128 different errors, and it is also common to replace them with 128 different characters, to make the decoding "lossless".

### Characteristics

Some of the important features of this encoding are as follows:

- Backward compatibility: Backward compatibility with ASCII and the enormous amount of software designed to process ASCII-encoded text was the main driving force behind the design of UTF-8. In UTF-8, single bytes with values in the range of 0 to 127 map directly to Unicode code points in the ASCII range. Single bytes in this range represent characters, as they do in ASCII. Moreover, 7-bit bytes (bytes where the most significant bit is 0) never appear in a multi-byte sequence, and no valid multi-byte sequence decodes to an ASCII code-point. A sequence of 7-bit bytes is both valid ASCII and valid UTF-8, and under either interpretation represents the same sequence of characters. Therefore, the 7-bit bytes in a UTF-8 stream represent all and only the ASCII characters in the stream. Thus, many text processors, parsers, protocols, file formats, text display programs, etc., which use ASCII characters for formatting and control purposes, will continue to work as intended by treating the UTF-8 byte stream as a sequence of single-byte characters, without decoding the multi-byte sequences. ASCII characters on which the processing turns, such as punctuation, whitespace, and control characters will never be encoded as multi-byte sequences. It is therefore safe for such processors to simply ignore or pass-through the multi-byte sequences, without decoding them. For example, ASCII whitespace may be used to tokenize a UTF-8 stream into words; ASCII line-feeds may be used to split a UTF-8 stream into lines; and ASCII NUL characters can be used to split UTF-8-encoded data into null-terminated strings. Similarly, many format strings used by library functions like "printf" will correctly handle UTF-8-encoded input arguments.

- Fallback and auto-detection: Only a small subset of possible byte strings are a valid UTF-8 string: several bytes cannot appear; a byte with the high bit set cannot be alone; and further requirements mean that it is extremely unlikely that a readable text in any extended ASCII is valid UTF-8. Part of the popularity of UTF-8 is due to it providing a form of backward compatibility for these as well. A UTF-8 processor which erroneously receives extended ASCII as input can thus "auto-detect" this with very high reliability. A UTF-8 stream may simply contain errors, resulting in the auto-detection scheme producing false positives; but auto-detection is successful in the vast majority of cases, especially with longer texts, and is widely used. It also works to "fall back" or replace 8-bit bytes using the appropriate code-point for a legacy encoding when errors in the UTF-8 are detected, allowing recovery even if UTF-8 and legacy encoding is concatenated in the same file.

- Prefix code: The first byte indicates the number of bytes in the sequence. Reading from a stream can instantaneously decode each individual fully received sequence, without first having to wait for either the first byte of a next sequence or an end-of-stream indication. The length of multi-byte sequences is easily determined by humans as it is simply the number of high-order 1s in the leading byte. An incorrect character will not be decoded if a stream ends mid-sequence.

- Self-synchronization: The leading bytes and the continuation bytes do not share values (continuation bytes start with the bits 10 while single bytes start with 0 and longer lead bytes start with 11). This means a search will not accidentally find the sequence for one character starting in the middle of another character. It also means the start of a character can be found from a random position by backing up at most 3 bytes to find the leading byte. An incorrect character will not be decoded if a stream starts mid-sequence, and a shorter sequence will never appear inside a longer one.

- Sorting order: The chosen values of the leading bytes means that a list of UTF-8 strings can be sorted in code point order by sorting the corresponding byte sequences.

#### Compared to single-byte encodings

- UTF-8 can encode any Unicode character, avoiding the need to figure out and set a " code page " or otherwise indicate what character set is in use, and allowing output in multiple scripts at the same time. For many scripts there have been more than one single-byte encoding in usage, so even knowing the script was insufficient information to display it correctly.

- The bytes 0xFE and 0xFF do not appear, so a valid UTF-8 stream never matches the UTF-16 byte-order mark (BOM) and thus cannot be confused with it. The absence of 0xFF (0377) also eliminates the need to escape this byte in Telnet (and FTP control connection).

- UTF-8 encoded text is larger than specialized single-byte encodings except for plain ASCII characters. In the case of scripts which used 8-bit character sets with non-Latin characters encoded in the upper half (such as most Cyrillic and Greek alphabet code pages), characters in UTF-8 will be double the size. For some scripts, such as Thai and Devanagari (which is used by various South Asian languages), characters will triple in size. There are even examples where a single byte turns into a composite character in Unicode and is thus six times larger in UTF-8. This has caused objections in India and other countries.

- It is possible in UTF-8 (or any other multi-byte encoding) to split or truncate a string in the middle of a character. If the two pieces are not re-appended later before interpretation as characters, this can introduce an invalid sequence at both the end of the previous section and the start of the next, and some decoders will not preserve these bytes and result in data loss. Because UTF-8 is self-synchronizing this will however never introduce a different valid character, and it is also fairly easy to move the truncation point backward to the start of a character.

- If the code points are all the same size, measurements of a fixed number of them is easy. Due to ASCII-era documentation where "character" is used as a synonym for "byte" this is often considered important. However, by measuring string positions using bytes instead of "characters" most algorithms can be easily and efficiently adapted for UTF-8. Searching for a string within a long string can for example be done byte by byte; the self-synchronization property prevents false positives.

#### Compared to other multi-byte encodings

- UTF-8 can encode any Unicode character. Files in different scripts can be displayed correctly without having to choose the correct code page or font. For instance, Chinese and Arabic can be written in the same file without specialized markup or manual settings that specify an encoding.

- UTF-8 is self-synchronizing: character boundaries are easily identified by scanning for well-defined bit patterns in either direction. If bytes are lost due to error or corruption, one can always locate the next valid character and resume processing. If there is a need to shorten a string to fit a specified field, the previous valid character can easily be found. Many multi-byte encodings such as Shift JIS are much harder to resynchronize. This also means that byte-oriented string-searching algorithms can be used with UTF-8 (as a character is the same as a "word" made up of that many bytes), optimized versions of byte searches can be much faster due to hardware support and lookup tables that have only 256 entries. Self-synchronization does however require that bits be reserved for these markers in every byte, increasing the size.

- Efficient to encode using simple bitwise operations. UTF-8 does not require slower mathematical operations such as multiplication or division (unlike Shift JIS, GB 2312 and other encodings).

- UTF-8 will take more space than a multi-byte encoding designed for a specific script. East Asian legacy encodings generally used two bytes per character yet take three bytes per character in UTF-8.

#### Compared to UTF-16

- Byte encodings and UTF-8 are represented by byte arrays in programs, and often nothing needs to be done to a function when converting source code from a byte encoding to UTF-8. UTF-16 is represented by 16-bit word arrays, and converting to UTF-16 while maintaining compatibility with existing ASCII-based programs (such as was done with Windows) requires every API and data structure that takes a string to be duplicated, one version accepting byte strings and another version accepting UTF-16. If backward compatibility is not needed, all string handling still must be modified.

- Text encoded in UTF-8 will be smaller than the same text encoded in UTF-16 if there are more code points below U+0080 than in the range U+0800..U+FFFF. This is true for all modern European languages. It is often true even for languages like Chinese, due to the large number of spaces, newlines, digits, and HTML markup in typical files.

- Most communication (e.g. HTML and IP) and storage (e.g. for Unix) was designed for a stream of bytes. A UTF-16 string must use a pair of bytes for each code unit: The order of those two bytes becomes an issue and must be specified in the UTF-16 protocol, such as with a byte-order mark (BOM). If an odd number of bytes is missing from UTF-16, the whole rest of the string will be meaningless text. Any bytes missing from UTF-8 will still allow the text to be recovered accurately starting with the next character after the missing bytes.

- The order of those two bytes becomes an issue and must be specified in the UTF-16 protocol, such as with a byte-order mark (BOM).

- If an odd number of bytes is missing from UTF-16, the whole rest of the string will be meaningless text. Any bytes missing from UTF-8 will still allow the text to be recovered accurately starting with the next character after the missing bytes.

## Implementations and adoption

UTF-8 has been the most common encoding for the World Wide Web since 2008. As of September 2024, UTF-8 is used by 98.3% of surveyed web sites. Although many pages only use ASCII characters to display content, very few websites now declare their encoding to only be ASCII instead of UTF-8. Over 50% of the languages tracked have 100% UTF-8 use.

Many standards only support UTF-8, e.g. JSON exchange requires it (without a byte-order mark (BOM)). UTF-8 is also the recommendation from the WHATWG for HTML and DOM specifications, and stating "UTF-8 encoding is the most appropriate encoding for interchange of Unicode " and the Internet Mail Consortium recommends that all e‑mail programs be able to display and create mail using UTF-8. The World Wide Web Consortium recommends UTF-8 as the default encoding in XML and HTML (and not just using UTF-8, also declaring it in metadata), "even when all characters are in the ASCII range... Using non-UTF-8 encodings can have unexpected results".

Lots of software has the ability to read/write UTF-8. It may though require the user to change options from the normal settings, or may require a BOM (byte-order mark) as the first character to read the file. Examples of software supporting UTF-8 include Microsoft Word, Microsoft Excel (2016 and later), Google Drive, LibreOffice and most databases.

Some software can only read and write UTF-8 (or at least does not require a BOM). Windows Notepad, in all currently supported versions of Windows, defaults to writing UTF-8 without a BOM (a change from the outdated / unsupported Windows 7 Notepad), bringing it into line with most other text editors. Some system files on Windows 11 require UTF-8 with no requirement for a BOM, and almost all files on macOS and Linux are required to be UTF-8 without a BOM. Java 18 defaults to reading and writing files as UTF-8, and in older versions (e.g. LTS versions) only the NIO API was changed to do so. Many other programming languages default to UTF-8 for I/O, including Ruby 3.0 and R 4.2.2. All current versions of Python support UTF-8 for I/O, even on Windows (where it is opt-in for the open() function), and plans exist to make UTF-8 I/O the default in Python 3.15 on all platforms. C++23 adopts UTF-8 as the only portable source code file format (surprisingly there was none before).

Backwards compatibility is a serious impediment to changing code to use UTF-8 instead of a 16-bit encoding, but this is happening. The default string primitive in Go, Julia, Rust, Swift 5, and PyPy uses UTF-8 internally in all cases. Python 3.3 uses UTF-8 internally for Python C API extensions and sometimes for strings and a future version of Python is planned to store strings as UTF-8 by default. Modern versions of Microsoft Visual Studio use UTF-8 internally. Microsoft's SQL Server 2019 added support for UTF-8, and using it results in a 35% speed increase, and "nearly 50% reduction in storage requirements."

All currently supported Windows versions support UTF-8 in some way (including Xbox); partial support has existed since at least Windows XP. As of May 2019, Microsoft has reversed its previous position of only recommending UTF-16; the capability to set UTF-8 as the "code page" for the Windows API was introduced; and Microsoft recommends programmers use UTF-8, and even states "UTF-16 is a unique burden that Windows places on code that targets multiple platforms".

The Java programming language includes Modified UTF-8 (MUTF-8), in which the null character (U+0000) uses the two-byte overlong encoding 110 00000 10 000000 (hexadecimal C0 80), instead of 00000000 (hexadecimal 00). Modified UTF-8 strings never contain any actual null bytes but can contain all Unicode code points including U+0000, which allows such strings (with a null byte appended) to be processed by traditional null-terminated string functions. All known Modified UTF-8 implementations also treat the surrogate pairs as in CESU-8. In normal usage, the language supports standard UTF-8 when reading and writing strings through InputStreamReader and OutputStreamWriter (if it is the platform's default character set or as requested by the program). However it uses Modified UTF-8 for object serialization among other applications of DataInput and DataOutput, for the Java Native Interface, and for embedding constant strings in class files. The dex format defined by Dalvik also uses the same modified UTF-8 to represent string values. Tcl also uses the same modified UTF-8 as Java for internal representation of Unicode data, but uses strict CESU-8 for external data.

Version 3 of the Python programming language treats each byte of an invalid UTF-8 bytestream as an error (see also changes with new UTF-8 mode in Python 3.7); this gives 128 different possible errors. Extensions have been created to allow any byte sequence that is assumed to be UTF-8 to be losslessly transformed to UTF-16 or UTF-32, by translating the 128 possible error bytes to reserved code points, and transforming those code points back to error bytes to output UTF-8. The most common approach is to translate the codes to U+DC80...U+DCFF which are low (trailing) surrogate values and thus "invalid" UTF-16, as used by Python 's PEP 383 (or "surrogateescape") approach. Another encoding called MirBSD OPTU-8/16 converts them to U+EF80...U+EFFF in a Private Use Area. In either approach, the byte value is encoded in the low eight bits of the output code point. These encodings are very useful because they avoid the need to deal with "invalid" byte strings until much later, if at all, and allow "text" and "data" byte arrays to be the same object. If a program wants to use UTF-16 internally these are required to preserve and use filenames that can use invalid UTF-8; as the Windows filesystem API uses UTF-16, the need to support invalid UTF-8 is less there. For the encoding to be reversible, the standard UTF-8 encodings of the code points used for erroneous bytes must be considered invalid. This makes the encoding incompatible with WTF-8 or CESU-8 (though only for 128 code points). When re-encoding it is necessary to be careful of sequences of error code points which convert back to valid UTF-8, which may be used by malicious software to get unexpected characters in the output, though this cannot produce ASCII characters so it is considered comparatively safe, since malicious sequences (such as cross-site scripting) usually rely on ASCII characters.

## Standards

There are several current definitions of UTF-8 in various standards documents:

- RFC 3629 / STD 63 (2003), which establishes UTF-8 as a standard internet protocol element

- RFC 5198 defines UTF-8 NFC for Network Interchange (2008)

- ISO/IEC 10646:2014 §9.1 (2014)

- The Unicode Standard, Version 15.0.0 (2022)

They supersede the definitions given in the following obsolete works:

- The Unicode Standard, Version 2.0, Appendix A (1996)

- ISO/IEC 10646-1:1993 Amendment 2 / Annex R (1996)

- RFC 2044 (1996)

- RFC 2279 (1998)

- The Unicode Standard, Version 3.0, §2.3 (2000) plus Corrigendum #1 : UTF-8 Shortest Form (2000)

- Unicode Standard Annex #27: Unicode 3.1 (2001)

- The Unicode Standard, Version 5.0 (2006)

- The Unicode Standard, Version 6.0 (2010)

They are all the same in their general mechanics, with the main differences being on issues such as allowed range of code point values and safe handling of invalid input.


Pompeia Helena

# Pompeia Helena

## Abstract

Pompeia Helena was a goldsmith, who worked in Rome during the time of the Roman Empire, around the first century CE.

## Death

Pompeia Helena is only known from her grave inscription in Rome, where she is identified as an aurifix (goldsmith). The inscription appears as part of the monument to Marcella, daughter of Octavia, which is found in the second section of the columbaria of Vigna Codini. She is believed to have been a freedwoman, from the Pompeia family.

The inscription reads:

Other artisans are found as part of the same monument, including: a margaritarius (pearl diver; pearl dealer), two vestiarii (clothes sellers), two unguentarii and a thurarius (frankincense dealer). The mosaic floor includes an inscription that indicates a terminus ante quem of 10 CE.

## Historiography

Pompeia Helen is not the only woman known to have worked as a goldsmith in Ancient Rome, others included: Serapa, Sellia Epyre, Vincentia. However, doubt has been placed on her role by John K Evans, who questioned whether aurifix means goldsmith in this context, or whether it might mean "custodian of gold ware".


2024–25 UD Las Palmas season

# 2024–25 UD Las Palmas season

## Abstract

The 2024–25 season is the 76th season in the history of the UD Las Palmas and the club's second consecutive season in La Liga. In addition to the domestic league, the team is scheduled to participate in the Copa del Rey.

## Players

### First-team squad

Note: Flags indicate national team as defined under FIFA eligibility rules. Players may hold more than one non-FIFA nationality.

## Transfers

## Friendlies

### Pre-season

## Competitions

### Overall record

Last updated: 15 September 2024 Source: Soccerway

### La Liga

#### League table

#### Results summary

Last updated: 15 September 2024. Source:

#### Results by round

#### Matches

The match schedule was released on 18 June 2024.