BIZTRAC BETA
Intermediation service activities for specialised retail sale

TERRA WATCHES BY EXPLORERS AS

Org. no. 929474252 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 53,000
Operating profit NOK 5,000
Equity NOK 35,000
Incorporated 2022
Share capital NOK 30,000

TERRA WATCHES BY EXPLORERS AS is registered as a limited company in Lillestrøm, Akershus with organisation number 929474252. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg og utvikling av klokker og ur og tilbehør til disse. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 53,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 53,000
Operating profit
NOK 5,000
Equity
NOK 35,000
Est. value
NOK 38,000

Financial health · 2024

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

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

Who owns TERRA WATCHES BY EXPLORERS AS?

LARS ERIK HANSEN
TERRA WATCHES BY EXPLORERS AS
NOK 53,000 rev. · NOK 5,000 profit

TERRA WATCHES BY EXPLORERS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TERRA WATCHES BY EXPLORERS AS

Who owns TERRA WATCHES BY EXPLORERS AS?

LARS ERIK HANSEN is the largest registered owner, with 55.3%.

What is the revenue of TERRA WATCHES BY EXPLORERS AS?

TERRA WATCHES BY EXPLORERS AS had revenue of NOK 53,000 in 2024.

Where is TERRA WATCHES BY EXPLORERS AS based?

TERRA WATCHES BY EXPLORERS AS has its business address in Lillestrøm.

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.