biztrac. BETA
COMPANY REGISTER PROFILE
930816272 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of machinery

SMITH SERVICETEKNIKK AS

Org. no. 930816272 Limited company (AS) Kristiansand Incorporated 2023 Active
Revenue 2025 NOK 1.0m
Operating profit NOK 142,000
Equity NOK 131,000
Incorporated 2023
Share capital NOK 30,000

SMITH SERVICETEKNIKK AS is registered as a limited company in Kristiansand, Agder with organisation number 930816272. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investere i andre selskaper. Reparasjoner og vedlikehold av maskiner og utstyr, samt kjøp og salg, og annet som naturlig hører til under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 142,000 in operating profit.

Former names: AFAS 300123-12 AS

Key figures · 2025

Revenue
NOK 1.0m
▲ +696 %
Operating profit
NOK 142,000
▲ +607 %
Equity
NOK 131,000
▲ +89 %
Est. value
NOK 387,000

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
43.6%
Very good
Return on total assets
Solidity
23.8%
Good
Equity as a share of total capital

Who owns SMITH SERVICETEKNIKK AS?

SMITH SERVICETEKNIKK AS
NOK 1.0m rev. · NOK 142,000 profit

SMITH SERVICETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMITH SERVICETEKNIKK AS

Who owns SMITH SERVICETEKNIKK AS?

Linn Anette Moberg Topstad is the largest registered owner, with 100.0%.

What is the revenue of SMITH SERVICETEKNIKK AS?

SMITH SERVICETEKNIKK AS had revenue of NOK 1.0m in 2025.

Where is SMITH SERVICETEKNIKK AS based?

SMITH SERVICETEKNIKK AS has its business address in Tveit.

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.