BIZTRAC BETA
Other technical consultancy

SANNER ENGINEERING AS

Org. no. 830737812 Limited company (AS) Balsfjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 46,000
Equity NOK 128,000
Incorporated 2023
Share capital NOK 30,000

SANNER ENGINEERING AS is registered as a limited company in Balsfjord, Troms with organisation number 830737812. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen Rådgivende Ingeniør - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 46,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 46,000
Equity
NOK 128,000
Est. value
NOK 293,000

Financial health · 2025

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

Who owns SANNER ENGINEERING AS?

JAN-FRODE SANNER
SANNER ENGINEERING AS
NOK 1.5m rev. · NOK 46,000 profit

SANNER ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANNER ENGINEERING AS

Who owns SANNER ENGINEERING AS?

JAN-FRODE SANNER is the largest registered owner, with 100.0%.

What is the revenue of SANNER ENGINEERING AS?

SANNER ENGINEERING AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SANNER ENGINEERING AS?

Jan-Frode Sanner is registered as general manager of SANNER ENGINEERING AS.

Where is SANNER ENGINEERING AS based?

SANNER ENGINEERING AS has its business address in Storsteinnes.

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.