Skip to content
Reality Check
Menu
Stage unconfirmed

Teltonika High-Tech Hill — AI data centre

Vilnius, Lithuania

Reviewed 13 Oct 20267 sources
Watch this site

Watch Teltonika High-Tech Hill — AI data centre

Register interest in updates to planning status, grid position, capacity claims, delivery teams and policy exposure. Every Power Reality Check client receives 60 days of Site Watch on their assessed site when monitoring is available.

Fields marked * are required.

Checking enquiry availability…

Request details

Register your interest in monitoring this record. Alerts are not active yet. Site Watch will cost €150 per site per month excluding VAT after any included trial.

Optional. Public information only. Do not include confidential or non-public information.

Project brief

Authority evidence preserves a later-phase AI data-centre intention within Teltonika's Vilnius technology-park programme. A 2023 concept placed it at Svylos g. 12, but the municipality now records a…

Read overview
Current evidenceStage unconfirmed

7 cited sources · 10 utility and planning categories reviewed.

Review evidence and gaps
Next check

Obtain a phase-specific demand application or allocation, firm/flexible terms, security and energisation milestones without summing transformer ratings.

Open the full check

Overview

Authority evidence preserves a later-phase AI data-centre intention within Teltonika's Vilnius technology-park programme. A 2023 concept placed it at Svylos g. 12, but the municipality now records a manufacturing project on that parcel; the current data-centre red line is therefore unresolved. The delivered 58 MW connection is for the technology park as a whole, not a data-centre allocation, and the two 63 MVA transformers are equipment ratings rather than additive import rights.

Developer / applicant
Teltonika group / High-Tech Hill programme
Owner
Not verified
Operator
Not verified

Planning and delivery status

The National Land Service says an AI data centre is planned in a later High-Tech Hill expansion phase. No project-specific application, exact current parcel, construction start or commissioning has been verified, so this remains an explicit pre-planning / unconfirmed record.

Stage source: 3 Sept 2026

Project intelligence. This record does not establish that the land or facility is available to acquire.

POWER STUDY

Power

What the power evidence establishes

The site-specific connection scope has not been established for this record.

Power classDNo qualifying rung

No same-scope, dated import-MVA rung has document-seen or better verification. Nearby infrastructure, IT MW and marketing claims cannot upgrade the class.

The class describes published documentary evidence at its stated date. It does not prove current contractual rights, transferability or an energisation date.

Class describes evidence maturity. Public records do not prove current contractual rights, transferable capacity or an energisation date. This record has not received a complete power study review.

Read the rules and verification levels
01

Capacity ladder and evidence

Each rung is a separate MVA claim for its stated site or phase. A missing rung is unknown.

01

Applied

Unknown

Not established from the public records reviewed.

What applied mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the applied connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the applied connection evidence cover?
Verification
Unknown
02

Offered

Unknown

Not established from the public records reviewed.

What offered mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the offered connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the offered connection evidence cover?
Verification
Unknown
03

Accepted / contracted

Unknown

Not established from the public records reviewed.

What accepted or contracted mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the accepted connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the accepted connection evidence cover?
Verification
Unknown
04

Energised

Unknown

Not established from the public records reviewed.

What energised mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the energised connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the energised connection evidence cover?
Verification
Unknown
Connection point and load boundaries
Network operator
Unknown

Not established from the public records reviewed.

Which TSO or DSO is responsible for this demand connection?
Connection point
Unknown

Not established from the public records reviewed.

What is the operator-confirmed connection substation or circuit?
Voltage
Unknown

Not established from the public records reviewed.

What voltage level is specified for the demand connection?
Straight-line distance
Unknown

Not established from the public records reviewed.

What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?
Published route length
Unknown

Not established from the public records reviewed.

What grid route length is published, and for which circuit?

IT load

Unknown

Not established from the public records reviewed.

What is the published IT load in MW?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the IT load in MW stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the IT load in MW cover?

Facility load

Unknown

Not established from the public records reviewed.

What is the published facility load in MW?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the facility load in MW stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the facility load in MW cover?

Import capacity

Unknown

Not established from the public records reviewed.

What is the published import capacity in MVA?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the import capacity in MVA stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the import capacity in MVA cover?

These are different electrical quantities. No power factor, PUE or available import is assumed from an IT-load statement.

Connection agreement and conditions
Agreement type
Unknown

Not established from the public records reviewed.

What connection agreement type and current status are documented?
Phased capacity
Unknown

Not established from the public records reviewed.

Does the agreement impose phased import-capacity limits?
Flexibility obligations
Unknown

Not established from the public records reviewed.

What flexibility or curtailment obligations apply?
On-site generation obligations
Unknown

Not established from the public records reviewed.

What on-site generation obligations apply?
Securities posted
Unknown

Not established from the public records reviewed.

What securities are required, posted and still valid?
Longstop dates
Unknown

Not established from the public records reviewed.

What connection longstop or milestone dates apply?
02

Conflicts and scope comparisons

No conflicting pair is recorded. This does not establish that all public statements have been reconciled.

03

Lithuania grid context

Network publications frame the claim. They do not allocate capacity to this site.

No country context entries have been linked to this site. Applicable policy, capacity information and reinforcement dependencies need review.

04

Derived energisation window

Earliest plausible yearUnknown
Latest plausible yearUnknown

The observed inputs do not establish a bounded delivery range. Open bounds stay unknown.

Rule

Use only a same-scope, dated, document-verified capacity rung and an applicable duration to energisation published by the observed site operator. The named process operator and a named source publisher must match that operator. Earliest year is the maximum of stage date plus minimum duration and each evidenced readiness constraint. Latest year is the maximum of stage date plus maximum duration and each published upper constraint only when every required input is bounded. An offer-processing duration is excluded. A missing required input leaves the affected bound unknown; no padding or contractual delivery promise is inferred.

No observed inputs establish this result.

Dependencies driving the range

  • Connection-dependent reinforcement scope and completion dates: unknown.
  • Grid-works planning status and programme: unknown.
  • Applicable connection-policy conditions and programme: unknown.

What the earliest case requires

  • Connection-dependent reinforcement scope and completion dates introduces no later constraint than the earliest case; this remains unverified.
  • Grid-works planning status and programme introduces no later constraint than the earliest case; this remains unverified.
  • Applicable connection-policy conditions and programme introduces no later constraint than the earliest case; this remains unverified.

Missing inputs leave the range open

  • A dated, document-verified import-MVA rung for the assessed scope.
  • An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.
  • Connection-dependent reinforcement scope and completion dates
  • Grid-works planning status and programme
  • Applicable connection-policy conditions and programme
05

Indicative HV and connection capex

Unknown

Rule and scope

Sum each published complete scope quantity multiplied by the matching published benchmark minimum and maximum. Configuration, voltage, route type, unit, country applicability, currency and explicit price base year must match. No assumed route length, transformer count, exchange rate, inflation, fee uplift or partial index is inserted. The result is an indicative benchmark band, not an operator quotation or contractual connection charge.

No observed inputs establish this result.

Published connection works scope
Unknown

Not established from the public records reviewed.

What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?
Scope completeness
Unknown

Not established from the public records reviewed.

Is the published connection scope complete enough to match every component to a sourced benchmark?

Scope questions

  • Obtain a published complete connection scope with voltage, configuration and measured quantities.
  • Establish that every necessary connection-work component is included in the published scope.
  • Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.
06

Alternatives and policy exposure

Behind-the-meter generation

Unknown

Not established from the public records reviewed.

What behind-the-meter generation is evidenced, and at what scope?
Planning / policy requirement
Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require behind-the-meter generation?

Battery storage

Unknown

Not established from the public records reviewed.

What battery storage is evidenced, and at what scope?
Planning / policy requirement
Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require battery storage?

Private wire

Unknown

Not established from the public records reviewed.

What a private wire is evidenced, and at what scope?
Planning / policy requirement
Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require a private wire?

Gas

Unknown

Not established from the public records reviewed.

What gas supply or generation is evidenced, and at what scope?
Planning / policy requirement
Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require gas supply or generation?

Connection claim against current policy

Unknown

Not established from the public records reviewed.

Does the published connection claim meet the policy applicable to its application date, location and agreement status?
07

Open questions for a Reality Check

Generated from unknown fields, missing derivation inputs and unresolved evidence. The questions identify the documents or specialist checks needed next.

60 questions to resolve
  1. Which TSO or DSO is responsible for this demand connection?

    Not established from the public records reviewed.

  2. What is the operator-confirmed connection substation or circuit?

    Not established from the public records reviewed.

  3. What voltage level is specified for the demand connection?

    Not established from the public records reviewed.

  4. What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?

    Not established from the public records reviewed.

  5. What grid route length is published, and for which circuit?

    Not established from the public records reviewed.

  6. What applied mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  7. What is the effective date of the applied connection evidence?

    Not established from the public records reviewed.

  8. Which buildings or phases does the applied connection evidence cover?

    Not established from the public records reviewed.

  9. What evidence level can be supported for capacityLadder.applied?

    Verification has not been established.

  10. What offered mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  11. What is the effective date of the offered connection evidence?

    Not established from the public records reviewed.

  12. Which buildings or phases does the offered connection evidence cover?

    Not established from the public records reviewed.

  13. What evidence level can be supported for capacityLadder.offered?

    Verification has not been established.

  14. What accepted or contracted mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  15. What is the effective date of the accepted connection evidence?

    Not established from the public records reviewed.

  16. Which buildings or phases does the accepted connection evidence cover?

    Not established from the public records reviewed.

  17. What evidence level can be supported for capacityLadder.accepted?

    Verification has not been established.

  18. What energised mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  19. What is the effective date of the energised connection evidence?

    Not established from the public records reviewed.

  20. Which buildings or phases does the energised connection evidence cover?

    Not established from the public records reviewed.

  21. What evidence level can be supported for capacityLadder.energised?

    Verification has not been established.

  22. What connection agreement type and current status are documented?

    Not established from the public records reviewed.

  23. Does the agreement impose phased import-capacity limits?

    Not established from the public records reviewed.

  24. What flexibility or curtailment obligations apply?

    Not established from the public records reviewed.

  25. What on-site generation obligations apply?

    Not established from the public records reviewed.

  26. What securities are required, posted and still valid?

    Not established from the public records reviewed.

  27. What connection longstop or milestone dates apply?

    Not established from the public records reviewed.

  28. What is the published IT load in MW?

    Not established from the public records reviewed.

  29. On what electrical basis is the IT load in MW stated?

    Not established from the public records reviewed.

  30. Which phase or campus does the IT load in MW cover?

    Not established from the public records reviewed.

  31. What is the published facility load in MW?

    Not established from the public records reviewed.

  32. On what electrical basis is the facility load in MW stated?

    Not established from the public records reviewed.

  33. Which phase or campus does the facility load in MW cover?

    Not established from the public records reviewed.

  34. What is the published import capacity in MVA?

    Not established from the public records reviewed.

  35. On what electrical basis is the import capacity in MVA stated?

    Not established from the public records reviewed.

  36. Which phase or campus does the import capacity in MVA cover?

    Not established from the public records reviewed.

  37. What operator-published connection-to-energisation duration applies to this site and connection stage?

    An application-to-offer processing target is not an energisation duration.

  38. Which reinforcements does the connection depend on, and what dates are published?

    Not established from the public records reviewed.

  39. Which grid works require planning, and what is their current consent status and dated programme?

    Not established from the public records reviewed.

  40. Which connection-policy conditions apply, and when could they be satisfied?

    Not established from the public records reviewed.

  41. What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?

    Not established from the public records reviewed.

  42. Is the published connection scope complete enough to match every component to a sourced benchmark?

    Not established from the public records reviewed.

  43. What behind-the-meter generation is evidenced, and at what scope?

    Not established from the public records reviewed.

  44. Does the applicable planning or connection policy require behind-the-meter generation?

    Not established from the public records reviewed.

  45. What battery storage is evidenced, and at what scope?

    Not established from the public records reviewed.

  46. Does the applicable planning or connection policy require battery storage?

    Not established from the public records reviewed.

  47. What a private wire is evidenced, and at what scope?

    Not established from the public records reviewed.

  48. Does the applicable planning or connection policy require a private wire?

    Not established from the public records reviewed.

  49. What gas supply or generation is evidenced, and at what scope?

    Not established from the public records reviewed.

  50. Does the applicable planning or connection policy require gas supply or generation?

    Not established from the public records reviewed.

  51. Does the published connection claim meet the policy applicable to its application date, location and agreement status?

    Not established from the public records reviewed.

  52. Which checked country-grid sources and location-specific constraints apply to this connection?

    No country-context relationship has been established for this record.

  53. Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.

    Connection-cost scope question.

  54. Resolve the energisation input: A dated, document-verified import-MVA rung for the assessed scope.

    This missing input leaves an energisation bound unknown.

  55. Resolve the energisation input: An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.

    This missing input leaves an energisation bound unknown.

  56. Resolve the energisation input: Connection-dependent reinforcement scope and completion dates

    This missing input leaves an energisation bound unknown.

  57. Resolve the energisation input: Grid-works planning status and programme

    This missing input leaves an energisation bound unknown.

  58. Resolve the energisation input: Applicable connection-policy conditions and programme

    This missing input leaves an energisation bound unknown.

  59. Obtain a published complete connection scope with voltage, configuration and measured quantities.

    This scope or reference gap prevents a complete indicative connection capex band.

  60. Establish that every necessary connection-work component is included in the published scope.

    This scope or reference gap prevents a complete indicative connection capex band.

Use these questions to scope a Power Reality Check.

Request an assessment of this record and the evidence needed next. Share only public information or documents you are authorised to provide.

Request a Reality Check
Earlier capacity notes and source context

No project-specific capacity figure is published in this record.

Import rights and connection evidence

Litgrid energised the Kuprioniškės 110 kV connection in September 2026. Up to 58 MW applies to the whole technology park; two 63 MVA transformers are individual equipment nameplates. Neither figure is an AI data-centre allocation or spare transferable import.

IT load, facility demand, import capacity and equipment ratings retain their stated scope. A published figure does not establish spare or transferable supply.

Planning & utilities

10 of 10 categories contain evidence. Each status applies to its specific claim.

Planning & decisions

Partial evidence

Government and land-authority sources retain an AI data centre in a later High-Tech Hill phase, but no project-specific application or permit was found. A 2023 Svylos g. 12 concept is not a current boundary because that address now has a manufacturing proposal.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Search Vilnius, TPDRIS and Infostatyba by project SPV and every expansion parcel; obtain the current red line and application before changing stage.

Land-use zoning

Partial evidence

The government-approved 14.82 ha plan changes Svylos Street expansion land toward industrial and storage use. The exact data-centre parcel and project-specific use assessment remain unresolved.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Retrieve the adopted regulations for K-NC-13-24-537 and match them to a current data-centre parcel.

Grid & import rights

Partial evidence

Litgrid energised the Kuprioniškės 110 kV connection in September 2026. Up to 58 MW applies to the whole technology park; two 63 MVA transformers are individual equipment nameplates. Neither figure is an AI data-centre allocation or spare transferable import.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Obtain a phase-specific demand application or allocation, firm/flexible terms, security and energisation milestones without summing transformer ratings.

Fibre & dark fibre

Unverified

No project-specific carrier, handoff, dark-fibre right, available pair or physically diverse route was identified.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Verify carrier commitments, duct ownership, entry points, shared sections, available pairs and contractual delivery dates for the eventual parcel.

Ownership & development control

Partial evidence

A 2023 municipality-hosted file describes UAB Power Group Property control over nearby plots. The later 0.3968 ha state lease is expressly for House of R&D. Neither establishes title or development control for the current AI data-centre parcel.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Identify the current parcel and match it to registered title or state lease, encumbrances and intra-group development rights.

Land, footprint & access

Partial evidence

The expansion plan covers 14.82 ha at Svylos g. 1 and 2, while the 2023 concept placed the data centre at Svylos g. 12. Later manufacturing use at Svylos g. 12 leaves the current red line and net area unresolved.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Reconcile the concept, expansion plan and cadastral parcels; obtain a current red line, access/easement schedule and net developable area.

Flood, ground & environment

Unverified

A plan-level decision not to require strategic environmental assessment does not replace project-level flood, ecology, noise, air, contamination or cumulative-impact review.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

After identifying the parcel, retrieve project-level EIA screening, flood/drainage, ecology, noise, air and cumulative assessments.

Water, cooling & heat

Unverified

No data-centre cooling design, water demand, utility agreement, discharge route or heat-reuse offtake was identified. Manufacturing-site utilities cannot be assigned to the data-centre phase.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Obtain the project-specific cooling concept, design conditions, water/wastewater terms, discharge route and any binding heat-reuse agreement.

Demand & location fit

Partial evidence

The sources establish an owner-led Teltonika AI data-centre intention, not a hyperscaler, neocloud or AI-lab customer. No compute contract, GPU deployment, reserved phase, IT load or open residual requirement is public.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Establish whether the facility is captive or third-party and seek a phase-specific workload, procurement or compute contract without inferring demand from the AI label.

Programme & delivery

Unverified

The wider campus has operating factories and delivered grid infrastructure, but no data-centre finance, design team, GC/MEP appointment, construction or commissioning programme was verified.

Sources & next check
Evidence reviewed 13 Oct 2026

Next check

Track project-specific finance, appointments, permit filing, construction start, power allocation and separate building, MEP and commissioning milestones.

Project team

Appointments are limited to the project, phase and scope supported by each source.

No project-specific team appointments have been verified for this record.

Sources

Publication dates are shown where known. Review dates do not establish approval or commissioning.

  1. Lithuanian Ministry of Economy and Innovation — approved 14.82 ha Svylos Street plan and AI data-centre intenteimin.lrv.lt · 4 Feb 2026
  2. National Land Service — High-Tech Hill lease and later-phase AI data-centre programmenzt.lrv.lt · 3 Sept 2026
  3. Vilnius municipality — 14.82 ha Svylos Street general-plan process K-NC-13-24-537vilnius.lt · 27 May 2025
  4. Vilnius municipality — 2023 High-Tech Hill concept showing a data centre at Svylos g. 12vilnius.lt · Publication date unstated
  5. Vilnius municipality — later manufacturing proposal at Svylos g. 12vilnius.lt · 17 Nov 2025
  6. Litgrid — completed Kuprioniškės 110 kV connection for High-Tech Hilllitgrid.eu · 16 Sept 2026
  7. Teltonika — High-Tech Hill campus and power infrastructureteltonika-iot-group.com · 16 Sept 2026

Original documents and maps retain their rights. Public access does not grant commercial redistribution rights.