Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/dbmpoolx/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/dbmpoolx/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ga-google-analytics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/dbmpoolx/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the js_composer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/dbmpoolx/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the eikra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/dbmpoolx/public_html/wp-includes/functions.php on line 6131
Dnyanbhasha Marathi Pratishthan | ज्ञानभाषा मराठी प्रतिष्ठान

✍️ गणिताशी गट्टी प्रश्न क्र. १०३ ✍️

✍️ गणिताशी गट्टी प्रश्न क्र. १०३ ✍️

 
एका व्यापाऱ्याने ७० रुपये किलो किमतीच्या २० किलो तांदळाच्या गोणीमध्ये ५५ रुपये किलो किमतीचे तांदूळ मिसळले आणि ते तांदूळ ७२ रुपये किलोने विकून २०% नफा कमावला. तर त्याने ५५ रुपये किलोचे किती किलो तांदूळ त्या गोणीत मिसळले होते?
 
➡️ उत्तर :- 
५५ रुपये किलोचे x किलो तांदूळ त्या गोणीत मिसळले होते असे मानू.
➡️ म्हणून,
x किलो तांदळाची खरेदी किंमत = ₹ ५५x
२० किलो तांदळाची खरेदी किंमत = २० × ७० = ₹ १४००
➡️ ५५ रुपये किलोचे x किलो तांदूळ त्या गोणीत मिसळल्यानंतर
१ किलो तांदळाची खरेदी किंमत = (५५x + १४००) / (x + २०)…(i)
गोणीतील तांदूळ ७२ रुपये किलोने विकून २०% नफा मिळवला आहे.
आपल्याला माहिती आहे की,
नफा = विक्री किंमत – खरेदी किंमत
         आणि
शेकडा नफा = १०० × नफा / खरेदी किंमत
२० = १००( विक्री किंमत – खरेदी किंमत) / खरेदी किंमत
२० × खरेदी किंमत = १००(७२ – खरेदी किंमत)
२० × खरेदी किंमत = ७२०० – १०० × खरेदी किंमत
२० × खरेदी किंमत + १०० × खरेदी किंमत = ७२००
१२० × खरेदी किंमत = ७२००
खरेदी किंमत = ७२००/१२०
➡️ म्हणून,
 
१ किलो तांदळाची किंमत = ₹ ६०…..(ii)
➡️ समीकरण (i) व (ii) वरून
६० = (५५x + १४००)/ (x + २०)
६०(x + २०) = (५५x + १४००)
६०x + १२०० = ५५x + १४००
६०x – ५५x = १४०० – १२००
५x = २००
x = २००/५
x = ४०
➡️ म्हणून ५५ रुपये किलोचे ४० किलो तांदूळ त्या गोणीत मिसळले होते.
 
 
 
© अजित तिजोरे – ८०९७६१७०२०
 
 
#ज्ञानभाषामराठीप्रतिष्ठान
#गणिताशी गट्टी

Leave a Reply

Your email address will not be published. Required fields are marked *