biztrac. BETA
COMPANY REGISTER PROFILE
917903816 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Floor and wall covering

FLISSERVICE AS

Org. no. 917903816 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −31,000
Equity NOK 39,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

FLISSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917903816. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Flislegging, vedlikehold bygg og hva dermed hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▲ +72 %
Operating profit
NOK −31,000
▲ +68 %
Equity
NOK 39,000
▼ −42 %
Est. value
NOK 724,000

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
-7.8%
Not satisfactory
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

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

Who owns FLISSERVICE AS?

FLISSERVICE AS
NOK 2.0m rev. · NOK −31,000 profit

FLISSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLISSERVICE AS

Who owns FLISSERVICE AS?

Stian Kulseth Brun is the largest registered owner, with 70.0%.

What is the revenue of FLISSERVICE AS?

FLISSERVICE AS had revenue of NOK 2.0m in 2025.

Who is the general manager of FLISSERVICE AS?

Stian Kulseth Brun is registered as general manager of FLISSERVICE AS.

Where is FLISSERVICE AS based?

FLISSERVICE AS has its business address in Ranheim.

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.