Land Records Logo

Land Records

Sullivan County, TN Parcels & GIS Data

Sullivan County, TN parcel data: 78,687 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Sullivan County, Tennessee parcel data covering 78,687 property records.

This page documents parcel-level coverage for Sullivan County, Tennessee. Each parcel record carries its boundary polygon (GIS geometry) along with attributes such as the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and most recent sale price and date. Exact fill rates for Sullivan County are listed in the attribute-coverage table below. Preview the data in the interactive explorer, or download the complete Sullivan County property dataset.

Sullivan County is a county located in the U.S. state of Tennessee on its northeast border. As of the 2020 census, the population was 158,163. Its county seat is Blountville.

FIPS 47163

Official county website: https://sullivancountytn.gov/

The FIPS code for Sullivan County is 47163.

Explore Sullivan County data
JohnsonCarterWashingtonHawkinsWashingtonScottBristolSullivan
Buy dataset · $185.00One-time downloadSubscribe · $325.001 year of quarterly updates

Attribute coverage

Sullivan County contains 78,687 parcels in the current dataset. Column coverage is the percentage of those parcels for which the attribute is populated (non-NULL).

ColumnCoverageRecords populated
lrid100%78,687
parcelid100%78,687
parcelid20.1%45
ogparcelid100%78,687
ogparcelid20.1%45
parentid<0.1%0
stackid<0.1%0
geoid100%78,687
statefp100%78,687
countyfp100%78,687
countyname100%78,687
cousubfp100%78,687
cousubname100%78,687
tractce100%78,687
tractname100%78,687
taxacctnum<0.1%3
taxyear<0.1%0
taxdistrict<0.1%10
usecode<0.1%10
usedesc<0.1%10
zoningcode<0.1%3
zoningdesc<0.1%0
numbldgs87.3%68,698
numunits<0.1%5
yearbuilt<0.1%10
numfloors<0.1%10
bldgsqft<0.1%0
bedrooms<0.1%10
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue<0.1%5
landvalue<0.1%10
agvalue<0.1%0
totalvalue<0.1%10
taxacres100%78,687
calcarea100%78,687
saleamt<0.1%6
saledate<0.1%10
ownertype100%78,653
ownername100%78,687
owneraddr<0.1%10
ownercity<0.1%10
ownerstate<0.1%10
ownerzip<0.1%10
parceladdr100%78,687
parcelcity100%78,687
parcelstate100%78,687
parcelzip100%78,687
legaldesc<0.1%20
township<0.1%0
section<0.1%0
qtrsection<0.1%0
range<0.1%0
plssdesc<0.1%0
book<0.1%10
page<0.1%10
block<0.1%0
lot100%78,677
parceltype2.2%1,725
accesstype2.2%1,725
iucnclass2.1%1,619
placename6.1%4,814
placetype6.0%4,753
firmid100%78,663
firmdate100%78,663
fldzone100%78,663
zonesubty97.6%76,797
staticbfe<0.1%3
elevmin99.8%78,506
elevmax99.8%78,506
elevavg99.8%78,506
fireplaces<0.1%0
heating<0.1%0
heatfuel<0.1%0
cooling<0.1%0
foundation<0.1%0
roofcover<0.1%0
siding<0.1%0
bldgtype<0.1%0
naicscode12.3%9,640
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated100%78,687
centroidx100%78,687
centroidy100%78,687
surfpointx100%78,687
surfpointy100%78,687
geom100%78,687
extras100%78,684
ownerlist<0.1%0

Schema mapping

How source columns from the acquired Sullivan County GIS layers map into the harmonized entity schemas and assemble into the published parcel table, alongside supplemented fields (elevation, flood zone) and deterministic columns.

Schema mapping — Sullivan County, Tennessee (47163) 1 entity · most recent acquisition per entity · generated 2026-07-25 direct column transformed (expression) geometry extras json supplemented determined ALL ENTITIES → FINAL PARCEL SCHEMA Harmonized entity columns assemble into publish.parcel_layer — matched by column name. Supplemented fields show their fill rate in this county. SOURCE COLUMNS HARMONIZED ENTITIES PUBLISH.PARCEL_LAYER PARCEL parcelid calc_acre owner address city lot lastupdate geom 16 cols ⇢ parcelid taxacres ownername parceladdr parcelcity lot updated geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname geom · derived from geometry geom dem.us_1m · USGS 1m DEM 100% elevmin 100% elevmax 100% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 97.6% zonesubty 0.0% staticbfe 100% firmdate 100% firmid supplemented · derived / other pipelines 87.3% numbldgs 100% parcelstate 100% parcelzip lrid parcelid ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname numbldgs taxacres calcarea ownertype ownername parceladdr parcelcity parcelstate parcelzip lot firmid firmdate fldzone zonesubty staticbfe elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras publish.parcel_layer columns not fed by these sources (57) — empty or below 50% fill in this county parcelid2, ogparcelid2, parentid, stackid, taxacctnum, taxyear, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numunits, yearbuilt numfloors, bldgsqft, bedrooms, halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, owneraddr, ownercity ownerstate, ownerzip, legaldesc, township, section, qtrsection, range, plssdesc, book, page, block, parceltype, accesstype, iucnclass placename, placetype, fireplaces, heating, heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit cwapermit, rcrapermit, ownerlist PARCEL 8 mapped · 16 kept in extras · 46 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL parcelid calc_acre owner address city lot lastupdate geom parcelid taxacres ownername parceladdr parcelcity lot updated geom extras · 16 source columns preserved as json gislink, county_id, parcel_type, file_type, conum, cmap, gp parcel, deedac, calcac, owner2, subdiv, shape_starea__ shape_stlength__, objectid_1, full_search_field extras not present in source — filled with NULL (46) parcelid2, taxacctnum, taxyear, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, saleamt, saledate, owneraddr, ownercity, ownerstate, ownerzip, parcelstate parcelzip, legaldesc, township, section, qtrsection, range, plssdesc, book, page, block, sourceurl, taxdistrict, parentid, fireplaces, heating cooling, foundation, roofcover, siding, heatfuel

Neighboring counties

Parcel data for counties bordering Sullivan County:

Frequently asked questions

Where can I find Sullivan County, TN parcel and GIS data?

Land Records publishes a Sullivan County, TN parcel dataset in which every parcel carries its boundary polygon (GIS geometry) along with ownership, assessed value, land use, acreage, and sale history. Preview it in the interactive explorer on this page, or download the full Sullivan County, TN dataset as a GeoPackage or CSV.

How many parcels are in Sullivan County, TN?

The current dataset contains 78,687 parcel records for Sullivan County, TN, each with its boundary geometry and assessor attributes.

What is the FIPS code for Sullivan County, TN?

The FIPS code for Sullivan County, TN is 47163.

What information does each Sullivan County, TN parcel record include?

Each Sullivan County, TN parcel record includes the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and the most recent sale price and date — plus the parcel boundary polygon. Per-attribute fill rates are listed in the coverage table on this page.

Is Sullivan County, TN parcel data free?

You can preview Sullivan County, TN parcels for free in the interactive explorer. The complete dataset is available as a one-time download or through the nationwide parcel web service; see the download options on this page for current pricing.

Does Sullivan County, TN have an official GIS or property records website?

Yes — the official Sullivan County, TN government website is linked in the county details above. Land Records standardizes Sullivan County, TN assessor and recorder records into a single nationwide parcel schema with GIS boundary geometry.

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated