biztrac. BETA
COMPANY REGISTER PROFILE
997077636 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

JARLEVEIEN 44 AS

Org. no. 997077636 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 944,000
Equity NOK 2.5m
Incorporated 2011
Share capital NOK 100,000

JARLEVEIEN 44 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997077636. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, drifte og å utvikle eiendom og hva som står i forbindelse med dette, herunder deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 944,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +2 %
Operating profit
NOK 944,000
▲ +0 %
Equity
NOK 2.5m
▲ +1 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
27.9%
Good
Equity as a share of total capital

Who owns JARLEVEIEN 44 AS?

JARLEVEIEN 44 AS
NOK 1.5m rev. · NOK 944,000 profit

JARLEVEIEN 44 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARLEVEIEN 44 AS

Who owns JARLEVEIEN 44 AS?

SANNUM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JARLEVEIEN 44 AS?

JARLEVEIEN 44 AS had revenue of NOK 1.5m in 2025.

Who is the general manager of JARLEVEIEN 44 AS?

Rune Sannum is registered as general manager of JARLEVEIEN 44 AS.

Where is JARLEVEIEN 44 AS based?

JARLEVEIEN 44 AS has its business address in Trondheim.

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.