biztrac. BETA
COMPANY REGISTER PROFILE
920459110 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of fabricated metal products

TOTEN BIL OG METALLRETUR AS

Org. no. 920459110 Limited company (AS) Østre Toten Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 11,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

TOTEN BIL OG METALLRETUR AS is registered as a limited company in Østre Toten, Innlandet with organisation number 920459110. The business is classified under repair and maintenance of fabricated metal products (NACE 33.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Satellittmottak av vrakbiler og mottak av jern, samt det som faller naturlig inn under dette.”.

Key figures · 2025

Operating profit
NOK −5,000
▲ +63 %
Equity
NOK 11,000
▼ −33 %
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns TOTEN BIL OG METALLRETUR AS?

TOTEN BIL OG METALLRETUR AS
· NOK −5,000 profit

TOTEN BIL OG METALLRETUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOTEN BIL OG METALLRETUR AS

Who owns TOTEN BIL OG METALLRETUR AS?

Tore Gudleik Berg is the largest registered owner, with 100.0%.

Who is the general manager of TOTEN BIL OG METALLRETUR AS?

Tore Gudleik Berg is registered as general manager of TOTEN BIL OG METALLRETUR AS.

Where is TOTEN BIL OG METALLRETUR AS based?

TOTEN BIL OG METALLRETUR AS has its business address in Lena.

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

Report a problem

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