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

ULLELITEN.NO AS

Org. no. 922941793 Limited company (AS) Bergen Incorporated 2019 Active
Revenue 2025 NOK 418,000
Operating profit NOK 78,000
Equity NOK 89,000
Incorporated 2019
Share capital NOK 30,000

ULLELITEN.NO AS is registered as a limited company in Bergen, Vestland with organisation number 922941793. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Netthandel med ull- og garnprodukter, oppskrifter og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 418,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2025

Revenue
NOK 418,000
▼ −19 %
Operating profit
NOK 78,000
▲ +166 %
Equity
NOK 89,000
▲ +656 %
Est. value
NOK 178,000

Financial health · 2025

Liquidity
159.49
Very good
Current assets ÷ current liabilities
Profitability
18.8%
Very good
Return on total assets
Solidity
21.3%
Weak
Equity as a share of total capital

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

Who owns ULLELITEN.NO AS?

ULLELITEN.NO AS
NOK 418,000 rev. · NOK 78,000 profit

ULLELITEN.NO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULLELITEN.NO AS

Who owns ULLELITEN.NO AS?

Silje Sandland Kjærgård is the largest registered owner, with 50.0%.

What is the revenue of ULLELITEN.NO AS?

ULLELITEN.NO AS had revenue of NOK 418,000 in 2025.

Who is the general manager of ULLELITEN.NO AS?

Silje Sandland Kjærgård is registered as general manager of ULLELITEN.NO AS.

Where is ULLELITEN.NO AS based?

ULLELITEN.NO AS has its business address in Mathopen.

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.