BIZTRAC BETA
Manufacture of other products of wood and articles of cork, straw and plaiting materials

SLOTTSGULV AS

Org. no. 890223222 Limited company (AS) Sandefjord Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 11.9m
Operating profit NOK 689,000
Equity NOK 2.8m
Incorporated 2006
Share capital NOK 100,000

SLOTTSGULV AS is registered as a limited company in Sandefjord, Vestfold with organisation number 890223222. The business is classified under manufacture of other products of wood and articles of cork, straw and plaiting materials (NACE 16.280). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg av trevarer og trevareprodukter og relaterte produkter, og det som naturlig hører sammen med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.9m in revenue and NOK 689,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.9m
Operating profit
NOK 689,000
Equity
NOK 2.8m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns SLOTTSGULV AS?

ESPEN CHRISTENSEN MOE
SLOTTSGULV AS
NOK 11.9m rev. · NOK 689,000 profit

SLOTTSGULV AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLOTTSGULV AS

Who owns SLOTTSGULV AS?

ESPEN CHRISTENSEN MOE is the largest registered owner, with 50.0%.

What is the revenue of SLOTTSGULV AS?

SLOTTSGULV AS had revenue of NOK 11.9m in 2024.

Who is the general manager of SLOTTSGULV AS?

Espen Christensen Moe is registered as general manager of SLOTTSGULV AS.

Where is SLOTTSGULV AS based?

SLOTTSGULV AS has its business address in Sandefjord.

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.