Marshall Amp Serial Number Lookup

Marshall amplifiers made hard rock possible. While Fender and Vox amps have their place in moving electrified guitar forward, the creations of Jim Marshall fostered an entirely new sound and allowed guitarists to fill stadiums with it.

Use the form below to share your questions, ideas, comments and feedback. Enter your phone number if you'd like to receive a call-back.

Marshall amps had such precedent-setting wattage and tone that their history can hardly be separated from the history of rock itself. We recently wrote an article detailing that rich history (which you can read here), but for those simply looking to figure out how old their Marshall amp is, we offer this shortcut. The guide below will help you quickly and clearly date Marshall amps and cabinets, without us waxing poetic about their influence. Before we begin, a few caveats: • Marshall model numbers look like years.

If your amp says Model 1986 on the inside, that does not mean it was made in 1986. This is probably the biggest area of confusion when dating Marshall amps.

• True serial numbers weren't really used by Marshall until July 1969, so specimens made prior to that can only be accurately dated to a fuzzy span of several years. • All Marshall amps originally came with Celestion speakers, so in cases where the speakers are original, can be used to date earlier amps. • Marshall cabinets didn't officially include serial numbers until October 1992.

As a result, dating cabs can be more art than science. The best approach is to cross-reference the serial number with known features for the model during different eras and the personal account of previous owners. Getting the correct year is one thing, but getting the story behind an amp is the fun part. Bleach Heat The Soul Ppsspp Android here.

The guide for that is much simpler: be nice, ask questions, offer beer. Marshall Amps By Series If you have absolutely no idea whether your Marshall is old or new, a good place to start is the model name or series.

This will give you an approximate idea of the era during which your amp was manufactured. It's also one more piece of evidence to pair with the serial number to corroborate the actual year. The first Marshall amps were made in England starting in 1962. Production has continued there uninterrupted through today, though some lower-priced models are now made in China, India or Korea, depending on the series. Valvestate Series: 1991 - 2000 AVT Series: 2000 - 2007 Mode Four Series: 2003 - 2008 MB Series: 2006 - 2012 Hand-Wired Reissue Series: 2004 - present JVM Series: 2007 - present Vintage Modern Series: 2007 - present Haze Series: 2009 - present MA Series: 2009 - present MG Series: 1999 - present JDM:1 Series: 2010 - present Some amps won't fit into these series (like the recent Class 5 Combo or various signature and limited edition models), so using the serial number will be your best bet to hone in on a specific date of manufacture. Marshall Serial Numbers To find the serial number on your Marshall amp, start by looking at the back panel of your amp. For models made between 1979 - 1981, the serial number will be on the front panel.

Keep in mind that no reliable serial number information exists for pre-1969 Marshall amps, so if your amp doesn't have a number matching one of the formats below, it is likely pre-1969 and identifiable by features rather than serial number. Click on the links here to jump directly to the serial number style that matches your instrument: • • • • • • Early Models: 1962 - 1964 The earliest Marshall amp models did not have model codes or any official serialization, though some models had a simple sequential four-digit numbering system inside the back panel. These numbers supposedly started with 1001 and progressed from there, starting with 2001 at the beginning of 1964. Often these specimens produced between October 1962 and December 1964 had an offset chassis. Look for original black levant covering, a gray grille and the old block-style Marshall logo. Model Codes Without Serial Numbers: 1965 - 1969 From January 1965 to June 1969, model codes were used but no known serial numbers accompanied them.

This era saw the advent of Plexiglas panels (giving rise to the 'Plexi' name) and four-digit model numbers. Amps from this era still have the block-style Marshall logo and a centered chassis. The model codes below should help you identify which model you have, while the characteristics described for each year should help with dating.

• Larger black cabinet feet circa July '69 (earlier feet were small and gray) Model Code-Serial-Date Code: 1969 - 1983 Starting in July 1969, Marshall starting using official serial codes. They were initially broken down into three parts: the model code, the serial production number and the date code. Marshall used letters as a date code to represent year of production. It's important to note that, prior to 1984, this letter came last. The letter B was skipped, as were the letters I, O and Q since they might be confused for numbers. Use the model codes and date codes below to determine the model and age of your amp.

For example, the number S/A 8481 E tells us that this is 50W amp (S/A) made in 1973 (E), production number 8481. J 1977 K 1978 L 1979 M 1980 N 1981 P 1982 R 1983 Model Code-Date Code-Serial: 1984 - 1992 From January 1984 to September 1992, the three-part coding was used by Marshall but the date code letter was moved from the end to the middle. The same model codes from the previous section of this article still apply, although the model code 'RI' is also seen for reissues. The additional date codes for this era are below. An example from this era might be SL/A X 10059.

This would indicate a 100W Super Lead (SL/A) built in 1989 (X), production number 10059. Date Codes 1984 - 1992. W 1988 X 1989 Y 1990 Z 1991 - 1992 Nine Digits On A Sticker: 1992 - 1997 Starting in October 1992, Marshall moved away from stamped metal plate serials and began using stickers with a xx-xxxxx-xx format serial and a bar code. Cabinets had serials at this point as well. The sticker-based nine digit scheme lasted through July 1997. These serials are much easier to understand, as they don't include any model or date codes. • The first two numbers indicate the last two digits of the year of production.

• The middle five numbers indicate the production number. • The last two numbers indicate the week of the year (01 - 52), out of 52 weeks. For example, the serial number 961002334 would tell us that this amp was made in 1996 (96), production number 10023, and it was made during the 34th (34) week of that year. Letter-Ten Digits-Letter: 1997 - Present Starting in August 1997, Marshall moved to their current serial number scheme, which is easier to understand and gives more information than previous schemes. These current serial numbers are arranged in a letter-ten digits-letter format (A-xxxx-xx-xxxx-A).

These are still found on stickers with a bar code on the back of the amp. • The first letter indicates where the amp was manufactured (M for England, C for China, I for India, K for Korea). • The next four digits indicate the year of production (1998, etc.).

• The next two digits indicate the week of the year during which the amp was produced (01 - 52). • The next four digits indicate the production number. • The final letter indicates the voltage setting (for use in different countries - see table below). For example, a serial number of M-20-B would indicate an amp made in England (M) in 2002 during the 38th week of the year, production number 1035, set up for use in the United States (B). Voltage Codes. A 230 Volts (UK) B 120/60 Volts (US) C 220/50 Volts (Canada) D 105/50/60 Volts (Japan) E 220/60 Volts (Europe) F 130/60 Volts (Mexico) Z Speaker cabs (no voltage) Celestion Speaker Codes: 1963 - Present If the speakers in your Marshall cabinet or combo are original, they can provide another piece of evidence when determining the date of manufacture. As many cabinets did not have official serial numbers before 1992, this can be especially helpful in dating earlier specimens.

Marshall has always used Celestion speakers standard from the factory, and thankfully, Celestion has been very consistent in coding their speakers. There have been three coding schemes used by Celestion since Marshall's birth as a company, each using some combination of day, month and year. Using the month and year codes below, and knowing what order they are in for different eras, you can easily decode a Celestion speaker's age.

Example: In the mid '60s the order was day-month-year, so a code showing 13DL would indicate a speaker made on the 13th of April, 1966. The month codes below remained consistent from 1963 forward, but there have been several eras of year codes. Check the era below that applies to your speaker. Celestion Month Codes. A January B February C March D April E May F June G July H August J September K October L November M December Celestion Year Codes: 1963 - 1967 During this four year stretch, Celestion speaker codes followed a day-month-year format. For example, a 12KM code would indicate a speaker made on the 12th of October (K) in 1967 (M). See the year codes below through 1967.

The year codes changed after this, so using other pieces of evidence to make sure you have pre-1968 speakers is important. If you have a speaker older than this, the year codes move backwards through the alphabet to A, which would be 1956. N 2003 P 2004 Q 2005 R 2006 S 2007 T 2008 U 2009 V 2010 W 2011 X 2012 Caveats, Exceptions, Gratitude The serial number is one part of the puzzle when dating an amp, but cross-checking the originality of the different parts, including tubes, wiring, transformers, knobs, etc.

Is just as important. If you're about to put down a hefty sum on a vintage Marshall, we strongly encourage you to consult multiple sources to determine the exact age and originality of the amp.

It should also be noted that there may be some signature models and limited editions that will vary slightly from the Marshall serial number formats described here, but in general, determining the year will be the same. We can hardly express enough how grateful we are for the hard work that the good folks at Vintage Marshall Amps website, Michael Doyle and Nick Bowcott, all of whom have done an immense amount of work to increase the accuracy and availability of information on Marshall amps.

WebSphere Application Server V7 now offers web server load balancing and failover for up to 5 licensed application servers and a new merge tool for simplifying load balancing and failover configurations. This is provided by way of a free fix pack available to all base version WebSphere Application Server V7 customers. Delivered in the WebSphere Application Server Fix Pack 13 (7.0.0.13) onwards are the new merge tool and an update to the WebSphere Application Server V7 License Agreement: • MergeTool - A multi-server auto configuration tool and documentation which helps you easily set up HTTP load balancing and failover to multiple WebSphere Application Server base servers.

For more details, see. • Updated License Agreement - An update to the WebSphere Application Server V7 License Agreement which relaxes the license restriction that previously allowed failover between only two WebSphere Application Server base servers to instead allow for HTTP load balancing and failover for up to 5 appropriately licensed servers. Description Administrative Console (all non-scripting) Information Disclosure in WebSphere Application Server Admin Console (CVE-2016-0377) Update the flags on the CSRF token cookie Unable to change maximum headers value in templates from administrative console. Description Administrative Console (all non-scripting) The console does not indicate when a new user is being created when adding a primary admin user. Renewing a personal certificate in RSA token keystore does not update a certificate alias name in security.xml. NullPointerException when opening memory-to-memory replication page in administrative console. Server running DPManager will not shut down on z/OS Data Replication Services Message CWWDR0008E Runtime exception occured: Unable to locate replication domain does not include the name of the domain.

Description Administrative Console (all non-scripting) Administrative console reports status of a running application as partial start after server restart. Update information returned from SOAP port Password field is blank in CSIv2 Outbound trusted identity Attempting to update an application from the administrative console returns error 500 and NumberFormatException From the console if you select everything under policy attachments it generates multiple entries in bindings.xml Mail validation is too strict for security notification emails WebSphere Application Server console clickjacking vulnerability 'Generic Servers' might remain as 'defunct' processes in the system after being stopped. Console provides a link to save the application even after it informed user they must discard the workspace.

Data Replication Services Delay in replication message delivery The members of the replication domain contains excessive members Default Messaging Component JMS message producer and consumer applications fail to produce and consume messages from service integration bus destination When MQ server is a bus member and correllationID of the message is used, queue is browsed against all messages. Restrict long running locks warning messages logged even though the feature is not enabled IllegalMonitorStateException leads to corrupt destination in WebSphere Application Server service integration bus MQ RFH2 header is propagated even though it is disabled at the destination. Dynamic Cache NumberFormatException in extended cache monitor Dynacache CWWDY1064E or DYNA1064E is written for containsKeyDisk() operation EJB Container Deadlock in com/ibm/ejs/util/cache/Cache.findAndFault and com/ibm/ejs/container/HomeRecord.getHomeAndInitialize( Federated Repositories Server startup has SECJ0363E and SECJ0369E errors Support for login policy to change password after first login in federated repository with LDAP repository configured. Duplicate predicates in LDAP query is causing performance issues for client.

NullPointerException while initializing the policy handler for openldap CWWIM4538E message improved to include repository IDs. General Follow-up to apar PM74190 for web services component WebSphere WOLA API calls failing with abend BBOX in BBOATRUE in a CICS TS 5.1 SAML web single-sign on (sso) may corrupt HTTP Request Parameter bytes SAML web single-sign on (sso) may redirect client to the wrong url SAML web single-sign on (sso) is corrupting NL characters on various actions/logins NullPointerException thrown from session manager code even though the application server is up and running.

When REU=Y some request to override a link succeed when all should fail Potential XSS vulnerability on session identifier handling when using url rewriting The JspWriterImpl is not properly cleaning up resources in memory after a request completes. HttpSessionBindingEvent.getValue() returns null A potential performance issue with ODR/Proxy on Microsoft Windows NullPointerException thrown when a session in memory was invalidated before the scheduled invalidation occured. Eclipse OSGi fails with exit code = 23. Include partition table information in logging. WSDL4J consumes excessive amounts of memory in the heap AdminTask.importSAMLIdPMetadata command generates invalid SAML Web SSO TAI properties Update the XML processing for portlet.xml during portlet application installation.

Double quotes are being seen in the installRegistryUtils.sh bat -listPackages command on French and Italian. With Java2 security on, the SECJ0314W is thrown. Application update failure with SaveFailureException and error IWAE0017E Followup to PM73096. Handle additional cases of archive memory leaks. High Availability (HA) PYT tables compatible with CICS TS 5.1 are missing BBOA8782E during ola processing of transactions with CHAR containers.

Add additional information for DCSV1115W IBM HTTP Server Detailed list of APARs for IBM HTTP Server. Component APAR Description 100% CPU Usage NullPointerException can occur in FFDC formatting of custom collections that introduce a null iterator. Deadlock encountered during server startup when attempting to process in-commit transactions Unable to adjust 3 sec makeconnection and 15 sec retry notification messages. WS-ReliableMessaging failures when concurrent work is processed WS-ReliableMessaging application causes java.lang.OutOfMemoryError due to large heap space usage WS-ReliableMesaging may cause CWSIP0801E message to be generated during messaging engine startup due to race condition. WS-ReliableMessaging scaleability issue in a clustered environment. La Maison Kabyle Bourdieu Pdf Free. Administrative Console (all non-scripting) Cannot uncheck enable JCA based inbound message delivery check box once checked in administrative console The administrative console always runs slowly whenever the node screen or log and trace screen panel is selected Console view last action incorrect and Jython error message is not useful.

Administrative console select all checkbox does not always work with Microsoft Internet Explorer 10 Login to the administrative console using j_security_script Creating cluster members results in duplicate ports. Administrative console does not accept valid thread pool field changes after editing server.xml Ok overwrites apply in administrative console on J2C authentication data settings PM78614 Administrative console URLs may be vulnerable to XSS attacks against logged-in users Extraneous test.jsp is shipped with the product. DB2 data source, automatic client reroute enabled, restart admin unsaved changes reported WebSphere Application Server.

Anonymous directories created by using the administrative console. PM79992 Security vulnerability when accessing the administrative console Increase in field selection size in 'share library mappings'. Component APAR Description 100% CPU Usage ClassCastException in LoadAvailableSequences following restart of a WS-Reliable messaging application. Remote server fails to be enlisted in transaction after ORB retry WS-Reliable messaging fails when SOAP message is requested Text in trace.log from job manager environment that should not be there Transaction alarms not cancelled during rollback of JCA transaction Server hang with web container threads waiting on com/ibm/ws/http/HttpTransport.reinitialize(HttpTransport.java:139) Recovery cannot be done and is being re-tried every 1 minute because not all applications are started. WAS reliable messaging stops forwarding requests after error NotOriginatorException occurs when accessing a WorkArea following a CORBA timeout.

ClassCastException thrown attempting to read servlet request with servlet caching enabled. Administrative Console (all non-scripting) A memory leak is possible when using diagnostic providers due to providers not being de-registered. Unable to see some connection factory settings as monitor role Administrative console should throw a warning or error message during application start, if the application fails to expand. Configuration error message CHKW2517E after displaying dmgr web container transport chains A mapping issue occurs with the name of the floating point encoding for the WMQ queue advanced panel In the administrative console, the HTTP Server config file (httpd.conf) is shown as a blank page.

Client policy set import fails on administrative console when authorization groups are defined Server_log_root variable in the updated cluster server template not honoring the user defined value. Binaries location field displayed incorrectly in the administrative console in some situations. Error message is displayed on the JMS providers administrative console page Administrative console issued JavaScript error when using Internet Explorer JavaScript error on Microsoft Internet Explorer when selecting &.