biztrac. BETA
COMPANY REGISTER PROFILE
922151903 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

MIKES GULVSLIPING AS

Org. no. 922151903 Limited company (AS) Kvinesdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 537,000
Operating profit NOK 28,000
Equity NOK 160,000
Incorporated 2019
Share capital NOK 30,000

MIKES GULVSLIPING AS is registered as a limited company in Kvinesdal, Agder with organisation number 922151903. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Snekring, gulvsliping og lakkering samt det som naturlig følger. Selskapet kan også delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 537,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 537,000
▼ −38 %
Operating profit
NOK 28,000
▲ +347 %
Equity
NOK 160,000
▲ +20 %
Est. value
NOK 156,000

Financial health · 2025

Liquidity
2.85
Very good
Current assets ÷ current liabilities
Profitability
11.6%
Good
Return on total assets
Solidity
66.0%
Very good
Equity as a share of total capital

Who owns MIKES GULVSLIPING AS?

MIKES GULVSLIPING AS
NOK 537,000 rev. · NOK 28,000 profit

MIKES GULVSLIPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIKES GULVSLIPING AS

Who owns MIKES GULVSLIPING AS?

Michael Nilsen is the largest registered owner, with 100.0%.

What is the revenue of MIKES GULVSLIPING AS?

MIKES GULVSLIPING AS had revenue of NOK 537,000 in 2025.

Who is the general manager of MIKES GULVSLIPING AS?

Michael Nilsen is registered as general manager of MIKES GULVSLIPING AS.

Where is MIKES GULVSLIPING AS based?

MIKES GULVSLIPING AS has its business address in Kvinesdal.

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.