BIZTRAC BETA
Joinery installation

STRØMMEN BYGGEPARTNERE AS

Org. no. 933903613 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 132,000
Operating profit NOK 61,000
Equity NOK 79,000
Incorporated 2024
Share capital NOK 30,000

STRØMMEN BYGGEPARTNERE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 933903613. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bygg og snekkerarbeid og alt som ligger under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 132,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2025

Revenue
NOK 132,000
Operating profit
NOK 61,000
Equity
NOK 79,000
Est. value
NOK 219,000

Financial health · 2025

Liquidity
1.94
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.7%
Weak
Equity as a share of total capital

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

Who owns STRØMMEN BYGGEPARTNERE AS?

AURIMAS SIMAITIS
STRØMMEN BYGGEPARTNERE AS
NOK 132,000 rev. · NOK 61,000 profit

STRØMMEN BYGGEPARTNERE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRØMMEN BYGGEPARTNERE AS

Who owns STRØMMEN BYGGEPARTNERE AS?

AURIMAS SIMAITIS is the largest registered owner, with 100.0%.

What is the revenue of STRØMMEN BYGGEPARTNERE AS?

STRØMMEN BYGGEPARTNERE AS had revenue of NOK 132,000 in 2025.

Who is the general manager of STRØMMEN BYGGEPARTNERE AS?

Aurimas Simaitis is registered as general manager of STRØMMEN BYGGEPARTNERE AS.

Where is STRØMMEN BYGGEPARTNERE AS based?

STRØMMEN BYGGEPARTNERE AS has its business address in Strømmen.

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.