BIZTRAC BETA
Other specialised construction activities n.e.c.

HANSEN OG JEPSEN AS

Org. no. 891574002 Limited company (AS) Vennesla Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 787,000
Equity NOK 1.4m
Incorporated 2007
Share capital NOK 100,000

HANSEN OG JEPSEN AS is registered as a limited company in Vennesla, Agder with organisation number 891574002. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Muring og forskaling, kjøp og salg av fast eiendom, eiendomsutvikling og utleie av eiendom, samt alt hva hermed står i forbindelse. Selskapet kan delta i andre selskap. ”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 787,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.2m
Operating profit
NOK 787,000
Equity
NOK 1.4m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns HANSEN OG JEPSEN AS?

RONNY BRYNJULFSEN HANSEN
HANSEN OG JEPSEN AS
NOK 14.2m rev. · NOK 787,000 profit

HANSEN OG JEPSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANSEN OG JEPSEN AS

Who owns HANSEN OG JEPSEN AS?

RONNY BRYNJULFSEN HANSEN is the largest registered owner, with 50.0%.

What is the revenue of HANSEN OG JEPSEN AS?

HANSEN OG JEPSEN AS had revenue of NOK 14.2m in 2025.

Who is the general manager of HANSEN OG JEPSEN AS?

Thomas Jenne Jepsen is registered as general manager of HANSEN OG JEPSEN AS.

Where is HANSEN OG JEPSEN AS based?

HANSEN OG JEPSEN AS has its business address in Vennesla.

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.