BIZTRAC BETA
Rental and operating of own or leased real estate

AGDER BILTILPASNING EIENDOM AS

Org. no. 986363343 Limited company (AS) Kristiansand Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 818,000
Equity NOK 689,000
Incorporated 2003
Share capital NOK 150,000

AGDER BILTILPASNING EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 986363343. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Handel, erverv, utleie og drift av eiendommer samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 818,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 818,000
Equity
NOK 689,000
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.4%
Good
Equity as a share of total capital

Who owns AGDER BILTILPASNING EIENDOM AS?

NITRAM HOLDING AS
AGDER BILTILPASNING EIENDOM AS
NOK 1.2m rev. · NOK 818,000 profit

AGDER BILTILPASNING EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AGDER BILTILPASNING EIENDOM AS

Who owns AGDER BILTILPASNING EIENDOM AS?

NITRAM HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of AGDER BILTILPASNING EIENDOM AS?

AGDER BILTILPASNING EIENDOM AS had revenue of NOK 1.2m in 2025.

Where is AGDER BILTILPASNING EIENDOM AS based?

AGDER BILTILPASNING EIENDOM AS has its business address in Kristiansand S.

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.