BIZTRAC BETA
Retail sale of textiles

SYBUTIKKEN LILLEHAMMER AS

Org. no. 986903291 Limited company (AS) Lillehammer Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 151,000
Equity NOK 1.5m
Incorporated 2004
Share capital NOK 100,000

SYBUTIKKEN LILLEHAMMER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 986903291. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Omsetning av symaskiner, tekstiler i metervare samt annet utstyr og tilbehør tilknyttet dette. Selskapet skal kunne eie fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 151,000
Equity
NOK 1.5m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns SYBUTIKKEN LILLEHAMMER AS?

BJØRN STENSETH
SYBUTIKKEN LILLEHAMMER AS
NOK 4.8m rev. · NOK 151,000 profit

SYBUTIKKEN LILLEHAMMER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYBUTIKKEN LILLEHAMMER AS

Who owns SYBUTIKKEN LILLEHAMMER AS?

BJØRN STENSETH is the largest registered owner, with 50.0%.

What is the revenue of SYBUTIKKEN LILLEHAMMER AS?

SYBUTIKKEN LILLEHAMMER AS had revenue of NOK 4.8m in 2025.

Who is the general manager of SYBUTIKKEN LILLEHAMMER AS?

Agnes Elisabeth Ramsrud is registered as general manager of SYBUTIKKEN LILLEHAMMER AS.

Where is SYBUTIKKEN LILLEHAMMER AS based?

SYBUTIKKEN LILLEHAMMER AS has its business address in Lillehammer.

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

Report a problem

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