BIZTRAC BETA
Intermediation service activities for specialised construction services

FLISLEGGER PÅ HJUL AS

Org. no. 831638702 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK 28,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLISLEGGER PÅ HJUL AS is registered as a limited company in Lillestrøm, Akershus with organisation number 831638702. The business is classified under intermediation service activities for specialised construction services (NACE 43.600). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremforhandle innkjøpsavtaler med grossister og leverandører for flisleggerbedrifter som er tilsluttet selskapet gjennom medlemskap.”.

Key figures · 2025

Operating profit
NOK −35,000
Equity
NOK 28,000
Est. value
NOK 28,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.7%
Weak
Equity as a share of total capital

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

Who owns FLISLEGGER PÅ HJUL AS?

KJEDEHUSET AS
FLISLEGGER PÅ HJUL AS
· NOK −35,000 profit

FLISLEGGER PÅ HJUL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLISLEGGER PÅ HJUL AS

Who owns FLISLEGGER PÅ HJUL AS?

KJEDEHUSET AS is the largest registered owner, with 100.0%.

Who is the general manager of FLISLEGGER PÅ HJUL AS?

Kai Johnsen is registered as general manager of FLISLEGGER PÅ HJUL AS.

Where is FLISLEGGER PÅ HJUL AS based?

FLISLEGGER PÅ HJUL AS has its business address in Lillestrøm.

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.