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

FATKI GULVSLIPER AS

Org. no. 934117662 Limited company (AS) Øystre Slidre Incorporated 2024 Active
Revenue 2025 NOK 1.0m
Operating profit NOK 165,000
Equity NOK 122,000
Incorporated 2024
Share capital NOK 30,000

FATKI GULVSLIPER AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 934117662. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vaktmestertjenester, og hva dermed står i forbindelse, herunder salg foruten investeringer og deltagelse i selskap med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 165,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +356 %
Operating profit
NOK 165,000
▲ +516 %
Equity
NOK 122,000
▲ +5050 %
Est. value
NOK 284,000

Financial health · 2025

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
45.0%
Very good
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns FATKI GULVSLIPER AS?

FATKI GULVSLIPER AS
NOK 1.0m rev. · NOK 165,000 profit

FATKI GULVSLIPER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FATKI GULVSLIPER AS

Who owns FATKI GULVSLIPER AS?

Hamode Fatki is the largest registered owner, with 100.0%.

What is the revenue of FATKI GULVSLIPER AS?

FATKI GULVSLIPER AS had revenue of NOK 1.0m in 2025.

Who is the general manager of FATKI GULVSLIPER AS?

Hamode Fatki is registered as general manager of FATKI GULVSLIPER AS.

Where is FATKI GULVSLIPER AS based?

FATKI GULVSLIPER AS has its business address in Skammestein.

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.