biztrac. BETA
COMPANY REGISTER PROFILE
934920589 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

NETTHANDELSHUSET AS

Org. no. 934920589 Limited company (AS) Lørenskog Incorporated 2025 Active
Revenue 2025 NOK 1.0m
Operating profit NOK 535,000
Equity NOK 441,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-06 Adresseendring registrert 2026-05-06.

NETTHANDELSHUSET AS is registered as a limited company in Lørenskog, Akershus with organisation number 934920589. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Postordre-/internetthandel med bredt vareutvalg.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 535,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 535,000
Equity
NOK 441,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns NETTHANDELSHUSET AS?

NETTHANDELSHUSET AS
NOK 1.0m rev. · NOK 535,000 profit

NETTHANDELSHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NETTHANDELSHUSET AS

Who owns NETTHANDELSHUSET AS?

Awais Munir is the largest registered owner, with 100.0%.

What is the revenue of NETTHANDELSHUSET AS?

NETTHANDELSHUSET AS had revenue of NOK 1.0m in 2025.

Who is the general manager of NETTHANDELSHUSET AS?

Awais Munir is registered as general manager of NETTHANDELSHUSET AS.

Where is NETTHANDELSHUSET AS based?

NETTHANDELSHUSET AS has its business address in Lørenskog.

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.