Yep, which equates (roughly) to about 4k per pageout -- an extremely negligible amount.
If one is seeing pageouts in the gigabyte range, that may be cause for concern (or at least it would be curious), but might be normal depending on what you're doing and what applications you're using.
Mac OS X manages memory much differently from the OS 7/8/9 days. Fragmented memory is not an issue anymore, and pageins/outs occur even with gobs of RAM to spare.
New *NIX users typically get concerned about this due to curiosity, much like they do over log entries: "My logs have entries that say 'Warning: deprecated function call statf() -- falling back to cached mode' and 'Error: std_f not found in library, will reload on next call' -- WHAT IS WRONG WITH MY COMPUTER WITH ALL THESE ERRORS AND WARNINGS?!"
Nothing is wrong with your computer. Programs throw warnings and errors constantly, and they're written to do those things purposefully. For example, if you "Save As..." and then click "Cancel" to cancel the operation, a log entry "Warning: User cancelled operation, looping backward to initial starting point" may be generated (or something similar). It's a program's responsibility to handle warnings and errors gracefully, so looking at the log files and freaking out about "Warning" and "Error" messages is typically moot.
Same with memory. With the dichotomy between "active" and "inactive" memory, "wired" and "free," "paged" and "nonpaged," etc., unless you know what those mean, looking at the numbers beside them won't give you any indication of proper or improper memory usage. Unless the computer is acting funny, more than likely, the memory usage you're seeing is perfectly normal and any ill feelings about those numbers probably stems from lack of understanding, and not an operational problem.