Uploading data!

Please wait...

Delisle to Fahrenheit

Calculates the Fahrenheit temperature from the given Delisle scale value
Type what you want to convert in the box below or
(autosubmits, max. 1MB)
<- ups! invalid URL! please, delete it or correct it!

Delisle to Fahrenheit

The Delisle temperature scale was defined by Joseph-Nicolas Delisle in 1732. This measure adjust 0 at the point of the boiling water and 150 as the freezing point of the water. The unit is represented by °D (and sometimes as °De) after the value.

The Fahrenheit temperature scale was proposed by Daniel Gabriel Fahrenheit in 1724 with the idea of starting from a brine solution freezes as 0, and 96 is the average temperature of human body. Its unit is represented with ℉ after the value.

The Fahrenheit degree values are calculated based on the formula $$212 - Delisle × {6 \over 5}$$

© by Lucentinian Works Co Ltd and ehehdada, ltd. 2018-2024

Jump to: ADLER32 | Base64 Decoder | Base64 Encoder | Binary values to Text | Celsius to Delisle | Celsius to Fahrenheit | Celsius to Gas Mark | Celsius to Kelvin | Celsius to Newton | Celsius to Rankine | Celsius to Réaumur | Celsius to Rømer | CRC32 | CRC32b | Decimal values to Text | Delisle to Celsius | Delisle to Fahrenheit | Delisle to Gas Mark | Delisle to Kelvin | Delisle to Newton | Delisle to Rankine | Delisle to Réaumur | Delisle to Rømer | Fahrenheit to Celsius | Fahrenheit to Delisle | Fahrenheit to Gas Mark | Fahrenheit to Kelvin | Fahrenheit to Newton | Fahrenheit to Rankine | Fahrenheit to Réaumur | Fahrenheit to Rømer | FNV132 | FNV1a32 | FNV164 | FNV1a64 | Gas Mark to Celsius | Gas Mark to Delisle | Gas Mark to Fahrenheit | Gas Mark to Kelvin | Gas Mark to Newton | Gas Mark to Rankine | Gas Mark to Réaumur | Gas Mark to Rømer | GOST | GOST-CRYPTO | Haval128,3 | Haval128,4 | Haval128,5 | Haval160,3 | Haval160,4 | Haval160,5 | Haval192,3 | Haval192,4 | Haval192,5 | Haval224,3 | Haval224,4 | Haval224,5 | Haval256,3 | Haval256,4 | Haval256,5 | Hex to text | HTML Entities Decoder | HTML Entities Encoder | Joaat | JSON Formatter and Beautifier | JSON Minimizer | Kelvin to Celsius | Kelvin to Delisle | Kelvin to Fahrenheit | Kelvin to Gas Mark | Kelvin to Newton | Kelvin to Rankine | Kelvin to Réaumur | Kelvin to Rømer | MD2 | MD4 | MD5 | Newton to Celsius | Newton To Delisle | Newton to Fahrenheit | Newton to Gas Mark | Newton to Kelvin | Newton To Rankine | Newton To Réaumur | Newton To Rømer | Octal values to Text | Rankine to Celsius | Rankine to Delisle | Rankine to Fahrenheit | Rankine to Gas Mark | Rankine to Kelvin | Rankine to Newton | Rankine to Réaumur | Rankine to Rømer | Réaumur to Celsius | Réaumur to Delisle | Réaumur to Fahrenheit | Réaumur to Gas Mark | Réaumur to Kelvin | Réaumur To Newton | Réaumur To Rankine | Réaumur To Rømer | RIPEMD128 | RIPEMD160 | RIPEMD256 | RIPEMD320 | Rømer to Celsius | Rømer to Delisle | Rømer to Fahrenheit | Rømer to Gas Mark | Rømer to Kelvin | Rømer to Newton | Rømer to Rankine | Rømer to Réaumur | ROT13 | SHA1 | SHA256 | SHA384 | SHA512 | SHA3-224 | SHA3-256 | SHA3-384 | SHA3-512 | Shuffle Characters | Snefru | Snefru256 | String/Text length | Text to Binary | Text to Decimal | Text to Hex | Text to Octal | Tiger128,3 | Tiger128,4 | Tiger160,3 | Tiger160,4 | Tiger192,3 | Tiger192,4 | To lowercase | To UPPERCASE | URL Decoder | URL Encoder | WHIRLPOOL | Date time text decoder to ATOM format | Date time text decoder to COOKIE format | Date time text decoder to ISO8601 format | Date time text decoder to RFC822 format | Date time text decoder to RFC850 format | Date time text decoder to RFC1036 format | Date time text decoder to RFC1123 format | Date time text decoder to RFC2822 format | Date time text decoder to RFC3339 format | Date time text decoder to RFC3339 EXTENDED format | Date time text decoder to RSS format | Date time text decoder to W3C format |

Cookies policy

This site is using third party cookies (Google Analytics, Zopim, and CoinImp), which are used mainly for statistics like counting the number of visitors from different places of the world, and settings.

We are not using them to identify particular users and we are not going to sell this data to anyone else, because it is used for our own understanding of our audience and improve our services.

For further questions, please don't hesitate to contact us.