biztrac. BETA
COMPANY REGISTER PROFILE
936887902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

WÅHLBERG ARCHIVE AS

Org. no. 936887902 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-22.

WÅHLBERG ARCHIVE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936887902. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Produksjon, markedsføring og salg av klær.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns WÅHLBERG ARCHIVE AS?

WÅHLBERG ARCHIVE AS
NOK 0 rev. · NOK 0 profit

WÅHLBERG ARCHIVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WÅHLBERG ARCHIVE AS

Who owns WÅHLBERG ARCHIVE AS?

Gabriel Listanco Einmo is the largest registered owner, with 100.0%.

What is the revenue of WÅHLBERG ARCHIVE AS?

WÅHLBERG ARCHIVE AS had revenue of NOK 0 in 2025.

Who is the general manager of WÅHLBERG ARCHIVE AS?

Gabriel Listanco Einmo is registered as general manager of WÅHLBERG ARCHIVE AS.

Where is WÅHLBERG ARCHIVE AS based?

WÅHLBERG ARCHIVE AS has its business address in Trondheim.

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.