BIZTRAC BETA
Rental and operating of own or leased real estate

LEVANGER RÅDHUS AS

Org. no. 943805806 Limited company (AS) Levanger Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 13.4m
Operating profit NOK 4.1m
Equity NOK 11.8m
Incorporated 1987
Share capital NOK 152,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LEVANGER RÅDHUS AS is registered as a limited company in Levanger, Trøndelag with organisation number 943805806. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 152,000, divided into 152 shares. The company's stated purpose is: “Bygge og eie forretnings-og kontorbygg i Levanger, samt annen virksomhet som står i naturlig forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.4m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 13.4m
Operating profit
NOK 4.1m
Equity
NOK 11.8m
Est. value
NOK 19.0m

Financial health · 2025

Liquidity
10.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns LEVANGER RÅDHUS AS?

LEVANGER KOMMUNE
LEVANGER RÅDHUS AS
NOK 13.4m rev. · NOK 4.1m profit

LEVANGER RÅDHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEVANGER RÅDHUS AS

Who owns LEVANGER RÅDHUS AS?

LEVANGER KOMMUNE is the largest registered owner, with 100.0%.

What is the revenue of LEVANGER RÅDHUS AS?

LEVANGER RÅDHUS AS had revenue of NOK 13.4m in 2025.

Where is LEVANGER RÅDHUS AS based?

LEVANGER RÅDHUS AS has its business address in Levanger.

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.