업데이트: 마지막으로 2025년 9월 3일에 Fix It Up 자동차 계층 리스트를 업데이트했습니다.
Fix It Up에서 복원된 자동차의 궁극적인 컬렉션을 만드는 것은 보람 있는 도전입니다. 가장 수익성 있는 프로젝트에 투자하려면 재정을 현명하게 관리해야 합니다. 이 가이드는 Fix It Up 자동차 계층 리스트를 제시하여 수익성 있는 선택을 할 수 있도록 도와줍니다.
Fix It Up 자동차 계층 리스트

위의 계층 리스트는 Fix It Up의 모든 자동차를 합리적인 수정 후 수익성에 따라 순위 매겼습니다. 일반적으로 비싼 자동차가 더 높은 수익을 내지만, 초기 게임 성공을 위해서는 저렴한 자동차를 구입하는 것이 필수적입니다.
완전한 Fix It Up 자동차 리스트
다음은 우리의 계층 리스트에 따라 순위가 매겨진 Fix It Up의 모든 자동차에 대한 자세한 목록입니다. 각 항목에는 가격, 이익 배수, 그리고 스폰 확률이 포함되어 있습니다.
S-티어 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
DOGO Desafio |
€450,000-€600,000 | 1.2x | 0.05% |
Fia-Te Double |
€15,000-€20,000 | 4x | 0.05% |
BNV K5 e60 |
€60,000-€90,000 | 1.2x | 0.5% |
BNV K4 G |
1.5x | N/A | |
Auidy V7 |
€50,000-€100,000 | 1.2x | 0.1% |
Auidy RF6 |
1.5x | N/A |
A-티어 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
Holde Inteiro |
€9,000-€30,000 | 1.5x | 7% |
Missah 750x |
€30,000-€55,000 | 1.2x | 1% |
BNV K3 e92 |
€45,000-€60,000 | 1.2x | 1% |
Merquis Z73 |
€35,000-€65,000 | 1.2x | 1% |
Auidy V5 |
€40,000-€55,000 | 1.2x | 1% |
Lokswag Golo GT |
€25,000-€55,000 | 1.2x | 2% |
Auidy RF3 |
€40,000-€55,000 | 1.2x | 0.6% |
B-티어 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
BNV K5 e39 |
€20,000-€50,000 | 1.2x | 3% |
Holde Ciwiq |
€5,000-€15,000 | 1.5x | 10% |
Missah Silva |
€15,000-€25,000 | 1.2x | 10% |
BNV K3 |
€9,000-€20,000 | 1.3x | 10% |
Leskus not200 |
€9,000-€20,000 | 1.3x | 10% |
Four Traffic |
€15,000-€35,000 | 1.3x | 6% |
C-티어 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
Auidy V4 |
€12,000-€18,000 | 1.3x | 15% |
Lokswag Passar |
€8,000-€14,000 | 1.3x | 20% |
Sacode Oitava |
€8,000-€14,000 | 1.3x | 20% |
Lokswag Golo |
€4,000-€8,000 | 1.5x | 30% |
Renas Kapturado |
€5,000-€11,000 | 1.3x | 30% |
D-티어 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
Siath Lion |
€1,500-€4,000 | 1.5x | 50% |
Peujo 200e6 |
€1,000-€4,000 | 1.5x | 50% |
Fia-Te Ponto |
€700-€3,000 | 1.5x | 50% |
Ontel Costa |
€700-€3,000 | 1.5x | 30% |
사용 불가능한 자동차
| 자동차 | 가격 | 이익 배수 | 스폰 확률 |
|---|---|---|---|
Mata FX7 |
1x | N/A | |
Porx JT3 RF |
1.5x | N/A | |
Banana Car |
관리자 자동차 | N/A | N/A |
Fix It Up에서 자동차 구매 및 판매 방법
-
고철 야적장에서는 매 5분마다 새로운 자동차가 나타납니다. -
구매 가능한 자동차는 일반적으로 녹슬기만 하고 대부분의 고철 차처럼 완전히 파손되지는 않습니다. -
고철 야적장에서 자동차를 클릭하여 구매할 수 있습니다. -
프리미엄 자동차 대리점은 고철 야적장 맞은편에 있습니다.
Fix It Up에서는 현금을 사용하여 자동차 고철 야적장 부지에서 새 차량을 획득할 수 있습니다. 재고는 일반 서버에서 매 5분마다, 개인 서버에서 매 4분마다 리프레시됩니다. 고철 야적장에 있는 자동차는 모두에게 동일하므로, 첫 번째로 도착한 플레이어가 자동차를 가져갑니다. DOGO Desafio와 같은 희귀한 자동차를 얻으려면 신속해야 합니다.
고철 야적장 맞은편에는 Robux를 사용하여 특별한 자동차를 구매할 수 있는 프리미엄 자동차 매장이 있습니다. 하지만 유한한 재고 때문에 판매를 고려하지 않는 것이 좋습니다.

자동차를 수리하고 커스터마이즈한 후에는 고철 야적장에서 몇 블록 떨어진 중고차 NPC에 판매할 수 있습니다. 또한, 향후 업데이트에서 플레이어가 커스텀 차량에 입찰할 수 있는 경매 기능이 추가될 예정입니다.
여기까지입니다—Fix It Up 자동차 계층 리스트에 대한 포괄적인 개요입니다. 가장 소중히 여기는 자동차는 무엇인가요? 추가 현금을 얻고 싶다면 Fix It Up 코드를 확인해 보세요.
가장 수익성 있는 자동차는 무엇인가요? DOGO Desafio와 Fia-Te Double를 구매하고 수정하면 가장 많은 이익을 얻을 수 있습니다.
초기 돈벌이에 가장 좋은 자동차는 무엇인가요? 게임 초반에는 Siath Lion, Lokswag Golo, BNV K3, Holde Ciwiq를 획득하고 수리하는 데 집중하세요.
프리미엄 자동차 매장에서 판매하기에 좋은 자동차가 있나요? 물론입니다! 하지만 비용과 한정된 재고 때문에 프리미엄 자동차는 수집용으로 보관하는 것이 가장 좋습니다.
자동차 제국을 탐험하고 확장해 나가세요! 더 많은 팁과 가이드를 원하시면 Moyens I/O를 방문하세요.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.





DOGO Desafio
Fia-Te Double
BNV K5 e60
BNV K4 G
Auidy V7
Auidy RF6
Holde Inteiro
Missah 750x
BNV K3 e92
Merquis Z73
Auidy V5
Lokswag Golo GT
Auidy RF3
BNV K5 e39
Holde Ciwiq
Missah Silva
BNV K3
Leskus not200
Four Traffic
Auidy V4
Lokswag Passar
Sacode Oitava
Lokswag Golo
Renas Kapturado
Siath Lion
Peujo 200e6
Fia-Te Ponto
Ontel Costa
Mata FX7
Porx JT3 RF
Banana Car













![THINK: The user wants to translate the title "Catch a Brainrot Tier List & Guide (RELEASE)" into Korean. I need to break down the key terms and concepts in the English title and find their appropriate Korean equivalents.
Catch a Brainrot: This is a playful, internet slang phrase.
"Brainrot" (뇌절) is a common internet slang in Korean, referring to something so cringey, overdone, or nonsensical that it makes your brain "rot" or shut down. It can also mean obsessing over something to an unhealthy degree.
"Catch a Brainrot" could be interpreted as "falling into brainrot," "getting brainrot," or simply "experiencing brainrot."
A common way to express "getting into / falling into [something bad/annoying/overdone]" in Korean internet slang is by using the noun and then implying the action. For example, "뇌절" itself can be used. Or, one might say "뇌절 각" (a situation ripe for brainrot), or "뇌절 유발" (brainrot-inducing).
However, "Catch a Brainrot" here seems to be the topic of the tier list. The tier list is about brainrot. So, maybe just referring to "brainrot" is enough.
Let's consider the nuance. "Catch a Brainrot" implies an action or a state. A tier list for brainrot items/situations.
Perhaps something like "뇌절 요소" (brainrot elements/factors) or "뇌절 유형" (brainrot types).
Or, simply using "뇌절" as the core concept.
If it's about identifying and categorizing different "brainrot" things, then "뇌절" as a concept is central.
"Catch a Brainrot" can be a bit tricky. Does it mean "how to get brainrot" or "how to identify brainrot"? Given the "Tier List & Guide," it's more likely about identifying and navigating different types of brainrot.
Let's try to capture the "catch" part. If it's about identifying or understanding brainrot.
"뇌절" is the direct translation for brainrot.
"잡다" (japda) means "to catch," but "뇌절을 잡다" doesn't sound natural in this context.
"뇌절에 대한" (about brainrot) or "뇌절 알아보기" (understanding brainrot).
Considering "Catch a Brainrot" as a playful, informal title, a direct translation might lose the feel.
Let's focus on what the tier list is. It's a tier list of brainrot-inducing things or brainrot situations. So the focus is on "brainrot."
Just "뇌절" might be sufficient as the object of the list.
Tier List: "티어 목록" (tieo mongnok) or "티어 리스트" (tieo riseuteu) are common. "등급표" (deunggeuppyo) is also possible for "tier list" or "ranking chart." "티어표" (tieopyo) is very common internet slang. "티어표" fits the informal tone better.
& Guide: "&" is often translated as "및" (mit), "그리고" (geurigo), or just omitted and implied by context. "Guide" is "가이드" (gaideu) or "안내서" (annaeseo). "가이드" is more common in such contexts.
(RELEASE): "(출시)" (chulsi), "(공개)" (gonggae), or "(발매)" (balmae). "(출시)" or "(공개)" are suitable for a content release. "(공개)" is perhaps more general for a release of information/content.
Combining them:
Option 1 (Focus on "brainrot" as the subject):
뇌절 티어표 & 가이드 (공개)
(Noejjeol tieopyo & gaideu (gonggae))
Option 2 (Trying to keep "catch"):
Is there a way to say "spotting brainrot" or "understanding brainrot" in a concise, slangy way?
"뇌절 잡기" (noejjeol japgi) - "catching brainrot," but again, "잡기" sounds like a game or a physical action.
"뇌절 포착" (noejjeol pochak) - "detecting/spotting brainrot," but "포착" is a bit too formal.
"뇌절 알아보기" (noejjeol arabogi) - "getting to know brainrot," "learning about brainrot."
"뇌절 공략" (noejjeol gongnyak) - "brainrot strategy/guide," implies how to deal with/understand brainrot. This is often used for game guides. This could fit "Catch a Brainrot Tier List & Guide."
Let's reconsider "Catch a Brainrot." If it's a guide for catching brainrot elements, then "뇌절 공략" or "뇌절 가이드" directly fits the "Guide" part.
The title is "Catch a Brainrot Tier List & Guide."
This implies the Tier List is about catching/understanding brainrot.
Let's break "Catch a Brainrot Tier List" as "뇌절 티어표." This means a tier list of brainrot.
Then "Guide" is just "가이드."
So, "뇌절 티어표 & 가이드" (Noejjeol tieopyo & gaideu) seems the most natural and concise translation for "Brainrot Tier List & Guide."
What about "Catch a"?
If the original was "How to Catch Brainrot: A Tier List & Guide," then "뇌절 잡는 법: 티어표 및 가이드" would be appropriate.
But it's "Catch a Brainrot Tier List & Guide." This phrasing suggests the tier list itself is a "catch a brainrot" type of list. It's almost like a category.
Perhaps "뇌절 캐치" (noejjeol kaechi - brainrot catch) could be integrated.
"뇌절 캐치 티어표 & 가이드" (Noejjeol kaechi tieopyo & gaideu)
"캐치" (kaechi) as in English "catch" is sometimes used for "catching on," "spotting," or "grabbing attention." This could work.
Let's compare:
뇌절 티어표 & 가이드 (공개) - Very direct, concise. "Brainrot Tier List & Guide (Release)." This implicitly covers "Catch a Brainrot" by making "brainrot" the subject of the list/guide.
뇌절 캐치 티어표 & 가이드 (공개) - Adds "캐치" which directly translates "Catch" and fits the informal tone. "Brainrot Catch Tier List & Guide (Release)." This explicitly states it's about catching or identifying brainrot.
Given the playful nature of "Catch a Brainrot," "뇌절 캐치" feels a bit more aligned with the original's intent of "spotting" or "identifying" brainrot items/situations. "캐치" is often used in Korean slang for "catching a glimpse," "catching on," or "spotting something."
Let's try to verify "뇌절 캐치". "밈 캐치" (meme catch) or similar phrases are used. It makes sense in an internet context.
So, the structure would be:
"Catch a Brainrot" -> 뇌절 캐치
"Tier List" -> 티어표
"& Guide" -> & 가이드
"(RELEASE)" -> (공개)
Putting it together:
뇌절 캐치 티어표 & 가이드 (공개)
Final check for plain text requirement:
"Return only the translated title as plain text. Do not include any explanations, additional text, formatting, or extra punctuation."
The chosen translation is "뇌절 캐치 티어표 & 가이드 (공개)". This fits all requirements.뇌절 캐치 티어표 & 가이드 (공개)](https://kr.moyens.net/wp-content/uploads/2026/07/1783863662_THINK-The-user-wants-to-translate-the-title-Catch-a-280x210.jpg)

![THOUGHT: The user wants to translate a title into Korean.
The title is "Haze Seas: Trello, Wiki & Discord Resources".
I need to break down the title into its components and translate each part.
Haze Seas: This sounds like a proper noun, possibly the name of a game, project, or community.
"Haze" can be translated as 안개 (an-gae).
"Seas" can be translated as 바다 (ba-da).
So, "Haze Seas" could be 안개 바다. If it's a fantasy name, sometimes direct translation works.
: (colon) - This is a separator, often kept as is or sometimes replaced by another connector in Korean if the flow requires it, but usually, a direct colon is fine, or contextually implied. However, the request specifically asks for plain text and no extra punctuation, so I should just translate the words and not add any extra punctuation like a colon if it's not explicitly part of the original word. The colon acts as a separator in the English title, so I should represent the relationship between the first part and the second part directly in Korean without adding a literal colon character in the final output. The instruction "Do not include any explanations, additional text, formatting, or extra punctuation" reinforces this.
Trello, Wiki & Discord Resources: This lists different types of resources.
Trello: This is a specific platform name, usually kept as is in Korean, written in Hangul. 트렐로 (teu-rel-lo).
Wiki: Also a specific platform/concept, usually kept as is in Korean, written in Hangul. 위키 (wi-ki).
&: "and". In Korean, this can be 와/과 (wa/gwa) or 및 (mit) or 그냥 (geu-nyang - just) or an implied 'and' by listing. Given it's a list of resources, '및' (and/as well as) is a good choice for connecting the last item in a list of categories.
Discord: Another platform name, kept as is in Korean, written in Hangul. 디스코드 (di-seu-ko-deu).
Resources: 자원 (ja-won - natural resources), 자료 (ja-ryo - data/material/resources), 리소스 (ri-so-seu - direct transliteration of resource, often used in IT/software contexts). For this context (Trello, Wiki, Discord for a project/community), 자료 or 리소스 would be appropriate. 자료 seems more natural for "information/guide resources".
Let's combine these:
Option 1 (direct translation, with implied colon/connection):
안개 바다: 트렐로, 위키 및 디스코드 자료
(Here, the colon is still present)
The instruction "Return only the translated title as plain text. Do not include any explanations, additional text, formatting, or extra punctuation." suggests I should not include the colon character if possible. I should try to make the Korean flow naturally without it.
Let's re-evaluate the structure without the colon:
"Haze Seas - Trello, Wiki & Discord Resources" implies "Resources for Haze Seas, specifically Trello, Wiki, and Discord ones." or "Haze Seas: These are the Trello, Wiki, and Discord resources related to it."
Korean sentence structure might be: "[Project Name] 관련 [Resource List] 자료" (Related [Resource List] Resources).
So, "[Haze Seas] 관련 트렐로, 위키 및 디스코드 자료"
안개 바다 관련 트렐로, 위키 및 디스코드 자료.
This sounds natural and avoids the colon.
Let's verify the "Haze Seas" translation again. If it's a proper noun, it might be better to transliterate or find a more common usage if it refers to a specific known entity. However, without more context, "안개 바다" (Fog Sea / Haze Sea) is a direct and reasonable translation for a name like "Haze Seas."
Let's consider "리소스" vs "자료". "리소스" is a direct transliteration and commonly used in IT/game contexts for "resources." "자료" is more general for "data/materials/information." Given Trello, Wiki, Discord are tools for managing information/materials, both work. "자료" might feel slightly more natural for "information resources" in a general sense. However, "리소스" is perfectly acceptable and often used. I'll go with 자료 for now.
So, the structure is:
[Project/Community Name] + [Connector for relatedness] + [List of platforms] + [Type of resources].
"Haze Seas" = 안개 바다
"related to" / "for" = 관련 (gwan-ryeon) or 의 (ui - possessive, less common here)
"Trello, Wiki & Discord" = 트렐로, 위키 및 디스코드
"Resources" = 자료
Combining:
안개 바다 관련 트렐로, 위키 및 디스코드 자료
This fits the "plain text" and "no extra punctuation" requirement as it directly translates the meaning without including the English colon.
Final check on the parts:
Haze Seas -> 안개 바다 (An-gae Ba-da)
Trello -> 트렐로 (Teu-rel-lo)
Wiki -> 위키 (Wi-ki)
Discord -> 디스코드 (Di-seu-ko-deu)
& -> 및 (mit - and, as well as)
Resources -> 자료 (ja-ryo - materials, data, resources)
The colon's function is to relate "Haze Seas" to the list of resources. "관련" (gwan-ryeon - related, concerning) serves this function naturally in Korean.
The translation "안개 바다 관련 트렐로, 위키 및 디스코드 자료" seems robust.안개 바다 관련 트렐로, 위키 및 디스코드 자료](https://kr.moyens.net/wp-content/uploads/2026/07/1783230518_THOUGHT-The-user-wants-to-translate-a-title-into-Korean-280x210.jpg)



