Error message

  • The specified file temporary://filed9Xs4Z could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileWlMPA8 could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileamtXUL could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filemFARYR could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileRpwfzt could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://file60GVck could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://file1PBaEw could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileZ7eUqS could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileCE9XzM could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileD6aRHf could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileB2ZfSB could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileFikXYc could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileb2CmO5 could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filetXy4VN could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filehtKT1D could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filebObDVm could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filecKHj8F could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filezB8mZy could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://filepRHB19 could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://file3UHEVe could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://file7RVu0P could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://fileSbp2cc could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
  • The specified file temporary://file65285R could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.

You are here

SRAM IPO on Hold

Published November 29, 2011

TAICHUNG, Taiwan—SRAM has put its plans to go public on the Nasdaq stock exchange on hold until at least next summer while it waits for volatility in the financial market to wane, Jeff Shupe, SRAM’s chief operating officer, said on Tuesday.

Shupe said waiting would also allow SRAM to project its 2013 earnings at the time of the initial public offering based on supplier orders for the following year’s product.

SRAM announced its intentions to go public back in May in order to raise capital to repay anticipated new company debt acquired to pay off the equity assets held by Trilantic Partners, a private equity firm that invested $234.8 million in SRAM in September 2008.

The following month, SRAM consolidated its debt in a new $790 million credit facility, of which $575 million was paid to Trilantic to regain its shares in the company.

SRAM has said it expects the IPO to raise approximately $300 million, but it’s never issued a specific date to list on the market. At this year’s Eurobike trade show, SRAM president Stan Day said going public would lay the financial foundation for future growth and announced his company’s intention to become the leader in urban bike drivetrain components in the next five years through internal gear hubs, external drivetrains for trekking and commuter bikes and a new electric bike drivetrain.

SRAM has not made any public announcement about any potential response to the electronic drivetrain innovations from competitors Shimano and Campagnolo.

—Nicole Formosa
nformosa@bicycleretailer.com