BIZTRAC BETA
Computer programming activities

MILESTECH AS

Org. no. 932771489 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1,000
Operating profit NOK −4,000
Equity NOK 8,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

MILESTECH AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932771489. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av innovative teknologiske produkter og tjenester. Herunder deltagelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 1,000
Operating profit
NOK −4,000
Equity
NOK 8,000
Est. value
NOK 6,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MILESTECH AS?

SEBASTIAN MILES HOLME
MILESTECH AS
NOK 1,000 rev. · NOK −4,000 profit

MILESTECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILESTECH AS

Who owns MILESTECH AS?

SEBASTIAN MILES HOLME is the largest registered owner, with 100.0%.

What is the revenue of MILESTECH AS?

MILESTECH AS had revenue of NOK 1,000 in 2024.

Who is the general manager of MILESTECH AS?

Sebastian Miles Holme is registered as general manager of MILESTECH AS.

Where is MILESTECH AS based?

MILESTECH AS has its business address in Skjetten.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.