• Hackathon Radar
Hackathons
  • Browse
  • Judge Opportunities
  • Sponsors
  • Organizers
  • Map
  • Discover
Personal
  • Custom Views
  • Passport
  • Favorites
Explore
  • Stats
  • State of Hackathons
  • Changelog
  • Settings

BIT-Techverse

unstopHosted on Unstop

Fetched 2 days ago

Wednesday, April 15, 2026

to Sunday, May 10, 2026

•

3 weeks long

AgritechHealthtechCybersecuritySocial ImpactInnovation
Student only
This hackathons is only open to students. Double check the event page for more information as this may mean only those from a particular university/country are eligible.

Event Type

in person

115

Participants

₹28,000

Prize Pool

10

Est. Projects

Focus Domains/Themes 1. Rural tech Agritech Fisheries and coastal solution 2. Medtech Health technology 3. Future tech Cybersecurity Energy conservation and digitalization   Hackathon Rulebook and Guidlines.Eligibility: Participation is open to students from technical backgrounds. Students from all colleges are allowed. Each team must consist of 2-4 members. Registration and Submission (Round 1): Required submissions: Presentation in (.pptx) format. Abstract (Max 500 words). Selected Domain. Find details related to ppt structure in ppt template. Shortlisting Criteria (Round 1): Innovation / Originality. Simplicity & Clarity. Real-World Applicability. Market Awareness (existing solutions considered) [ONLY FOR BIT STUDENTS]. On Campus Hackathon Rules: Case study rules: All shortlisted teams must work ONLY on the assigned case study. Teams cannot continue or reuse their original submitted idea. Duration: Total hackathon duration: 24 hours. Resting accommodations will be provide. Development Rules: Allowed: Open-source resources. APIs (e.g., AI, cloud services, etc.). Internet access. NOT allowed: Pre-built projects or complete solutions. Pre-written core logic/code before hackathon. Mandatory Github repo submission: Teams must submit a GitHub repository link BEFORE case study allocation. This repo should be empty or contain only basic setup. Violation Consequences: Immediate disqualification. Penalty/Fine imposed by organizers. Fair Play and Plagiarism: Any form of plagiarism or copying will result in: Immediate disqualification. Additional penalties (if applicable).     Guidelines: Round 1: Idea Submission Guidelines Teams must submit a PPT (.pptx) and a 500-word abstract PPT must not exceed 8 slides Submissions must follow the prescribed slide structure Submission Rules Ideas must be original and clearly defined Solutions must be practical and implementable Direct copies of existing solutions will be penalized No fully developed projects allowed Evaluation Criteria Innovation & originality Simplicity & clarity Real-world applicability Awareness of existing solutions Important Notes Shortlisting is based only on submitted PPT & abstract Selected teams will proceed to the on-campus hackathon Shortlisted teams must be ready to adapt to a new case study Round 2: Mid Evaluation Guidelines Round 2 will be conducted on-campus during the hackathon Teams will be assigned a domain-specific case study (previously failed solution) Teams must work ONLY on the assigned case study Objective Analyze a failed solution Identify gaps and limitations Propose an improved and feasible approach Team Requirements Understand the given case study thoroughly Research existing approaches (if required) Redefine the problem based on identified gaps Design a clear and improved solution approach  Mid Evaluation (Presentation) Teams must present: Key gaps in the previous solution Reasons for failure Proposed solution approach How the new solution overcomes previous limitations Rules Teams cannot revert to their Round 1 idea Solution must directly address the assigned case study No pre-built solutions allowed All progress must be developed during hackathon hours  Evaluation Criteria Problem analysis & gap identification Understanding of previous failure Strength and clarity of proposed solution Logical reasoning and feasibility  Important Notes This is a checkpoint round (not final judging) Feedback from judges may be provided Teams are expected to refine and continue building after this round Disqualification Ignoring the assigned case study Lack of meaningful analysis Evidence of pre-built or copied solutions  

Judge Accessibility

Organizer email available25/25
Student-run event15/15
Actively looking for judges25/25
Small event (120 participants)10/10
No corporate sponsors10/10
New or emerging organizer10/10
Public registration available5/5
Online format (judge from anywhere)10/10

Top signals

Organizer email available
Student-run event
Actively looking for judges

Organizers

Alex Johnson

alex@example.org

Jamie Rivera

jamie@example.org

Sam Chen

sam@example.org

Estimated Audience

Mostly Students
ExperienceStudent
OccupationStudents
Beginner Friendly
Women in Tech

Technical Focus

AI95%
Web80%
Mobile25%

Industries

Healthcare
Education
Climate

Technologies

Python
React
OpenAI

Why this estimate

  • • Hosted by a university
  • • Open to students
  • • MLH member event

Estimate inferred from event metadata, not actual attendee data.

Quality Score

Quality Score

72/100
High confidence
Organiser16/20
Event Maturity14/20
Sponsors18/25
Participants12/20
Operations12/15

Why this score

Strong organiser track record
Returning event
Well-sponsored

Missing data

Prize details
Code of conduct