biztrac. BETA
COMPANY REGISTER PROFILE
939284699 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

A PAULSEN & SØNNER AS

Org. no. 939284699 Limited company (AS) Ibestad Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 556,000
Equity NOK 2.6m
Incorporated 1985
Employees 8
Share capital NOK 1.9m

A PAULSEN & SØNNER AS is registered as a limited company in Ibestad, Troms with organisation number 939284699. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1985 and has 8 registered employees. Registered share capital is NOK 1.9m, divided into 770 shares. The company's stated purpose is: “Anleggsvirksomhet med maskiner, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 556,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
▼ −12 %
Operating profit
NOK 556,000
▲ +466 %
Equity
NOK 2.6m
▲ +25 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
2.33
Very good
Current assets ÷ current liabilities
Profitability
13.1%
Good
Return on total assets
Solidity
58.2%
Very good
Equity as a share of total capital

Who owns A PAULSEN & SØNNER AS?

A PAULSEN & SØNNER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about A PAULSEN & SØNNER AS

Who owns A PAULSEN & SØNNER AS?

Stian Jenssen Paulsen is the largest registered owner, with 23.4%.

What is the revenue of A PAULSEN & SØNNER AS?

A PAULSEN & SØNNER AS had revenue of NOK 7.8m in 2025.

Who is the general manager of A PAULSEN & SØNNER AS?

Stian Jenssen Paulsen is registered as general manager of A PAULSEN & SØNNER AS.

Where is A PAULSEN & SØNNER AS based?

A PAULSEN & SØNNER AS has its business address in Engenes.

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.