BIZTRAC BETA
Floor and wall covering

SANDSTRÖMS GULVSERVICE AS

Org. no. 993567914 Limited company (AS) Kongsvinger Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 33,000
Equity NOK 34,000
Incorporated 2009
Share capital NOK 30,000

SANDSTRÖMS GULVSERVICE AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 993567914. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Gulvlegging og alt som hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 33,000
Equity
NOK 34,000
Est. value
NOK 127,000

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.7%
Weak
Equity as a share of total capital

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

Who owns SANDSTRÖMS GULVSERVICE AS?

BO ANDERS LINDBERG SANDSTRÖM
SANDSTRÖMS GULVSERVICE AS
NOK 2.0m rev. · NOK 33,000 profit

SANDSTRÖMS GULVSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDSTRÖMS GULVSERVICE AS

Who owns SANDSTRÖMS GULVSERVICE AS?

BO ANDERS LINDBERG SANDSTRÖM is the largest registered owner, with 100.0%.

What is the revenue of SANDSTRÖMS GULVSERVICE AS?

SANDSTRÖMS GULVSERVICE AS had revenue of NOK 2.0m in 2025.

Who is the general manager of SANDSTRÖMS GULVSERVICE AS?

Bo Anders Lindberg Sandström is registered as general manager of SANDSTRÖMS GULVSERVICE AS.

Where is SANDSTRÖMS GULVSERVICE AS based?

SANDSTRÖMS GULVSERVICE AS has its business address in Kongsvinger.

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.