Contact

LOGNORM.DIST in ONLYOFFICE: Lognormal CDF and Density with Log-Scale Inputs

Statistical Intermediate ONLYOFFICE

Use LOGNORM.DIST with clear model inputs, independently calculated examples, exact-version source limits and compatibility guidance.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

=LOGNORM.DIST(10,LN(10),0.5,TRUE) has the independent target 0.5. The arguments describe the mean and standard deviation of the natural logarithm, not the ordinary mean and spread of the positive values.

Syntax

LOGNORM.DIST(x, mean, standard_dev, cumulative)

Build a fictional positive-duration model

Create DurationModel. Put Parameter in A1 and Value in B1, then enter these values and one formula:

Cell Parameter Enter
B2 Mean of natural logarithms, μ =LN(10)
B3 Standard deviation of natural logarithms, σ 0.5
B4 Low duration, minutes 5
B5 Median duration, minutes 10
B6 High duration, minutes 20
B7 Left-tail probability 0.95

This is an assumed lognormal model for a fictional task duration, not observed data. If X is the duration measured numerically in minutes, ln(X) is modeled as normal with mean μ and standard deviation σ. Use natural logarithms, not base-10 logarithms. The numerical unit must stay consistent when transforming data.

Here exp(μ)=10 is the median, not the arithmetic mean duration. The arithmetic mean is exp(μ+σ²/2), approximately 11.3314845306683 minutes; the mode is exp(μ−σ²), approximately 7.78800783071405. Entering 10 as the mean argument instead of LN(10) specifies a radically different model. A positive skew does not by itself prove real data follow a lognormal distribution.

Choose probability or density

The official reference has four required arguments. TRUE returns a left-tail cumulative probability, P(X≤x). FALSE returns a continuous density. A density is a height per unit of duration; it is not the probability of finishing at one exact minute. For a continuous model, the probability at an exact point is zero.

For positive x, standardize the logarithm as z=(ln(x)−μ)/σ. The CDF is Φ(z), while the density is φ(z)/(σx). The extra division by x is essential; simply using a normal density for ln(x) does not give the density of X.

Worked duration results

Cell Formula Independent target
D2 =LOGNORM.DIST(B4,B2,B3,TRUE) 0.0828285190016984
D3 =LOGNORM.DIST(B5,B2,B3,TRUE) 0.5
D4 =LOGNORM.DIST(B6,B2,B3,TRUE) 0.917171480998301
D5 =D4-D2 0.834342961996603
D6 =1-D4 0.0828285190016986
D7 =LOGNORM.DIST(B5,B2,B3,FALSE) 0.0797884560802865
D8 =LOGNORM.DIST(B6,B2,B3,FALSE) 0.0152613826047546

D5 is the modeled share between 5 and 20 minutes. Those endpoints are equally spaced around LN(10) on the log scale, not around 10 on the original scale. D7 and D8 are densities; do not format them as a percentage of tasks taking exactly 10 or 20 minutes.

Advanced: verify the transformation

In F2 put =(LN(B6)-B2)/B3, with target about 1.38629436111989. =NORM.S.DIST(F2,TRUE) has the same mathematical CDF target as D4. For density, =NORM.S.DIST(F2,FALSE)/(B3*B6) reconstructs D8. These are mathematical checks, not evidence of identical rounding in a running editor.

A time-unit conversion changes the logarithmic mean. If minutes are multiplied by 60 to obtain seconds, add LN(60) to μ and keep σ unchanged. Merely multiplying μ by 60 would be wrong. Percentiles scale with the original duration units, whereas the spread of logarithms does not change under this constant multiplication.

Boundary and legacy differences

Help restricts x to positive values. The pinned code is more permissive in the cumulative branch: with σ>0, x≤0 returns 0. Thus =LOGNORM.DIST(0,LN(10),0.5,TRUE) is source-predicted 0, while the same call with FALSE is source-predicted #NUM!. A nonpositive σ is rejected in both modes. These boundary observations are version-pinned source facts, not native measurements.

LOGNORMDIST is a three-argument cumulative-only function and rejects x≤0. Do not treat the two interfaces as interchangeable punctuation variants. The modern path also uses array-oriented preparation, whereas the legacy path selects the first element of explicit arrays; no spill workflow is established here.

The CDF uses 0.5+gauss on the standardized log value. The source’s normal-helper comment warns of cancellation in sufficiently negative tails. Avoid inferring high relative accuracy for extremely small probabilities from the moderate examples above. Errors in argument conversion propagate; use explicit TRUE or FALSE rather than undocumented numeric coercion of the mode.

Version, precision and verification

Checked October 18, 2026 against current official help and SDKJS tag v10.0.0.169, commit 3679e0375a758d7dc59d31337a45461be3525ed8. Introduction dates and a final supported-version endpoint are not established. Desktop Editors, Docs, mobile releases and imported files require separate compatibility checks.

Neither the ONLYOFFICE application nor its calculation engine was executed for this guide. The numerical targets are independently calculated mathematical values; code-path and error observations are manual source traces. They are not screenshots, displayed workbook results or promises of identical final digits. Use English function names and comma separators as shown, adapting separators to the editor’s locale.

Keep inputs and intermediate probabilities numeric and unrounded. Format the display rather than replacing values with rounded strings. These moderate scalar examples do not certify extreme-tail accuracy, unusual type coercion, array entry or dynamic spill. Model assumptions must be checked separately from arithmetic correctness.