semkuFinal grade calculator
Enter your current grade, final-exam weight and target grade to find the score you need.
Calculation rules
Required final-exam score = (target grade − current grade × (1 − w)) / w, where w is the final-exam weight divided by 100.
This model uses one final exam and the current grade for all other coursework. Feasibility assumes final-exam scores from 0% to 100%; a result above 100% is not attainable, and a result below 0% means the target is already secured under this model.
The required score is rounded once to two decimal places, with ties rounded away from zero. Feasibility is checked before rounding; your course's grading and rounding rules determine the score actually awarded.
Frequently asked questions
- What do I need if my current grade is 85%, the final is worth 20% and my target is 87%?
- You need 95.00% on the final: (87 − 85 × 0.8) / 0.2 = 95.
- Why does the required score exceed 100%?
- Your target cannot be reached under this model if the final exam is capped at 100%. With a current grade of 85%, a final weight of 20% and a target of 90%, the required score is 110.00%.
- What does a negative required score mean?
- The coursework already contributes more than your target, so a final score of 0% or more secures it under this model. With a current grade of 85%, a final weight of 20% and a target of 60%, the result is −40.00%; it is not a score you need to earn.
- What should I enter as my current grade?
- Enter the grade for the coursework before the final, not an overall grade that already includes a placeholder score for the final exam.
Privacy on this page
Calculations run in your browser. The values you enter are not sent to the server or saved in browser storage. Reloading the page returns the inputs to their initial state.
To understand how the page is used and to improve the service, this page sends semku’s own usage statistics and automatic error reports. They go only to the dedicated endpoint under semku.com/api/telemetry/v1/. They are not used for advertising or third-party tracking.
The usage statistics include the stage of use (such as starting an operation or requesting a copy), the time it happened and fixed identifiers that distinguish the page and feature. They do not include the values you enter, the results shown or the text you copy. Inputs are not sent as hashes or as size categories either. The full URL and search terms are not sent.
Operations and sessions are distinguished by randomly generated identifiers. In the browser these exist only in temporary memory and are not written to cookies or browser storage. No identification based on cookies or combined device characteristics is used.
Error reports contain the error type, code and time, and, where available, a registered program-source identifier with the line and column number. The error message text and stack traces are not sent. Usage statistics and error reports also carry the site identifier, the published build and a random record identifier. For access records such as IP addresses, browser signals (User-Agent Client Hints), region and language, see the paragraph below.
The feedback form sends the rating you chose and the text you typed in the free-text field when you press the send button. A random ID that distinguishes the submission, the page, site and published build, and the type of request are also sent. There are no fields for your name, email address or phone number, and the values you enter are not attached automatically. Whatever you write in the free-text field is sent as is. Please do not enter personal data, passwords, authentication keys or payment details.
To improve the service, we record the country and state/province-level region at the time of your visit (an estimate based on the connecting network), which site you came from including the page path, and one display-language setting announced by your browser (for example, en-US). Location is kept to country and region only; no city or precise position is recorded. When you use the service, connection records, including your IP address, are automatically generated and retained to maintain service security and identify abnormal access. Cloudflare is the data processor for this site. Collection of this item is enabled only after this notice is published; we do not collect it retrospectively for use before collection is enabled. Query strings such as search terms are not recorded, and neither is the full list of preferred languages or the raw request headers. To identify bots, we may collect and use signals your browser reports about its type and version, along with an indication of whether automation tools are being used. These browser signals are estimates and do not conclusively identify your browser's type or version or whether automation tools are being used. Collection of this information is currently disabled and will only be enabled after this notice is published. We do not collect it retrospectively for use before collection is enabled. The raw User-Agent request header is not recorded. These records are per visit only and use no identifier that links one visit to another. Recording starts only with visits after this notice is published and is not applied retroactively to earlier visits. The region and the referring site have been recorded since 2026-09-20; the display language since 2026-09-24. Browser signals are not recorded yet.
Separately, when you visit the site, the hosting provider records your IP address, the time of the request and user-agent information about your browser and device in Cloudflare Pages’ standard access logs.
For details, see the privacy policy in Korean.
Calculations run in your browser without sending your calculation inputs or results to the server. See “Privacy on this page” for information about access data.