Type to search

Sterling College (Vermont)

Craftsbury Common, Vermont•4-year•Private

Your chances

-

Acceptance rate

100%

Private school in Vermont with fewer than 200 total undergraduate students
Rural
New England
On campus housing
sterlingcollege.edu
16 Sterling Drive, Craftsbury Common, VT 05827
(802) 586-7711
verified
Work at Sterling College (Vermont)?
Verify your profile

Admissions

Overall acceptance rate
100%
Yield rate - overall
41%

Acceptance rate breakdown

Women
100%
Men
100%

Applicant breakdown

Total number of applicants
41
Women: 65%
Men: 35%
sterlingcollege.edu/admissions

Cost & scholarships

Your estimated net cost
$ ? / year
In-state
$49,600
Out-of-state
$49,600

Published costs and averages can be misleading: they don’t fully account for your family’s finances (for financial aid) or your academic profile (for scholarships).

Want to see your personalized net cost after financial aid and scholarships?

Applications

How to apply

Accepts Common App
Test not used
Rec letters not used
Considers class rank
TOEFL required (international applicants)
Policies can change. Please confirm by looking at this school’s website.

Do you work at Sterling College (Vermont)?

Verify your profile to keep your college's data up to date, get insights on user activity and connect with hand raiser students

Verify your profile

Students

First-year enrolled students (full-time)
17
Student diversity
Moderately diverse
4-year graduation rate
75%
6-year graduation rate
75%
Retention rate
57%
Admission policy
Co-ed
International students
2%

Enrolled breakdown by gender

Women: 52%
Men: 48%

Race & ethnicity diversity

Among domestic students
Asian and Pacific Islander
1%
Black
1%
Hispanic
3%
Native American
1%
Other
34%
White
59%

Academics

Student faculty ratio
7:1
Calendar system
Semester

Special academic offering

Study abroad

Credit for AP exams

Academic and career counseling

Where does this data come from?
Do you work at a school?
Verify your profile

Missing API endpoint:

The client-side code needs access to API endpoint , but it wasn't defined.

Did you forget to call the client_side_endpoints helper?