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

PERLEHUSET AS

Org. no. 977046424 Limited company (AS) Vestby Incorporated 1996 Active
Revenue 2025 NOK 806,000
Operating profit NOK 1,000
Equity NOK 2.0m
Incorporated 1996
Share capital NOK 540,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PERLEHUSET AS is registered as a limited company in Vestby, Akershus with organisation number 977046424. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 1996. Registered share capital is NOK 540,000, divided into 5400 shares. The company's stated purpose is: “Internetthandel med knapper, sysaker og hobbyprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 806,000 in revenue and NOK 1,000 in operating profit.

Former names: ARIES AS

Key figures · 2025

Revenue
NOK 806,000
▲ +0 %
Operating profit
NOK 1,000
▼ −100 %
Equity
NOK 2.0m
▼ −10 %
Est. value
NOK 962,000

Financial health · 2025

Liquidity
2.71
Very good
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
41.7%
Very good
Equity as a share of total capital

Who owns PERLEHUSET AS?

PERLEHUSET AS
NOK 806,000 rev. · NOK 1,000 profit

PERLEHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERLEHUSET AS

Who owns PERLEHUSET AS?

KVIST HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PERLEHUSET AS?

PERLEHUSET AS had revenue of NOK 806,000 in 2025.

Who is the general manager of PERLEHUSET AS?

Anka Kvist is registered as general manager of PERLEHUSET AS.

Where is PERLEHUSET AS based?

PERLEHUSET AS has its business address in Vestby.

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.