BIZTRAC BETA
Other construction installation

SMERUD INVEST AS

Org. no. 934783697 Limited company (AS) Ullensaker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 965,000
Operating profit NOK 25,000
Equity NOK 44,000
Incorporated 2024
Share capital NOK 30,000

SMERUD INVEST AS is registered as a limited company in Ullensaker, Akershus with organisation number 934783697. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg, installasjon og service av elektroniske sikkerhetssystemer, deltagelse i andre selskaper og virksomheter, samt annet som naturlig står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 965,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 965,000
Operating profit
NOK 25,000
Equity
NOK 44,000
Est. value
NOK 105,000

Financial health · 2025

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

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

Who owns SMERUD INVEST AS?

CHRISTIN SMERUD
SMERUD INVEST AS
NOK 965,000 rev. · NOK 25,000 profit

SMERUD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMERUD INVEST AS

Who owns SMERUD INVEST AS?

CHRISTIN SMERUD is the largest registered owner, with 100.0%.

What is the revenue of SMERUD INVEST AS?

SMERUD INVEST AS had revenue of NOK 965,000 in 2025.

Who is the general manager of SMERUD INVEST AS?

Christin Smerud is registered as general manager of SMERUD INVEST AS.

Where is SMERUD INVEST AS based?

SMERUD INVEST AS has its business address in Jessheim.

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.