BIZTRAC BETA
Construction of residential and non-residential buildings

JACOBSEN SNEKKERSERVICE AS

Org. no. 975858847 Limited company (AS) Trondheim Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 20.3m
Operating profit NOK 1.3m
Equity NOK 3.4m
Incorporated 1995
Employees 13
Share capital NOK 100,000

JACOBSEN SNEKKERSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 975858847. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1995 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekker- og entreprenørvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 20.3m
Operating profit
NOK 1.3m
Equity
NOK 3.4m
Est. value
NOK 6.3m

Financial health · 2024

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.6%
Very good
Equity as a share of total capital

Who owns JACOBSEN SNEKKERSERVICE AS?

GEIR JACOBSEN HOLDING AS
JACOBSEN SNEKKERSERVICE AS
NOK 20.3m rev. · NOK 1.3m profit

JACOBSEN SNEKKERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JACOBSEN SNEKKERSERVICE AS

Who owns JACOBSEN SNEKKERSERVICE AS?

GEIR JACOBSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of JACOBSEN SNEKKERSERVICE AS?

JACOBSEN SNEKKERSERVICE AS had revenue of NOK 20.3m in 2024.

Who is the general manager of JACOBSEN SNEKKERSERVICE AS?

Geir Jacobsen is registered as general manager of JACOBSEN SNEKKERSERVICE AS.

Where is JACOBSEN SNEKKERSERVICE AS based?

JACOBSEN SNEKKERSERVICE AS has its business address in Bosberg.

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.