BIZTRAC BETA
COMPANY REGISTER PROFILE
989146718 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TEWLE AS

Org. no. 989146718 Limited company (AS) Øvre Eiker Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −138,000
Equity NOK 5.0m
Incorporated 2005
Share capital NOK 102,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−138k kr).

TEWLE AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 989146718. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Kjøp, salg, investeringer i aksjer og andre verdipapirer samt fast eiendom med dertil tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −138,000
▼ −18 %
Equity
NOK 5.0m
▲ +7 %
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns TEWLE AS?

TEWLE AS
· NOK −138,000 profit

TEWLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEWLE AS

Who owns TEWLE AS?

TOR ERIKSEN is the largest registered owner, with 100.0%.

Who is the general manager of TEWLE AS?

Tor Eriksen is registered as general manager of TEWLE AS.

Where is TEWLE AS based?

TEWLE AS has its business address in Hokksund.

Property

Business address Dueveien 6, 3302 Hokksund
Cadastral unit 3314-73/106/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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