BIZTRAC BETA
Construction of residential and non-residential buildings

TTN ENTREPRENØR AS

Org. no. 933861384 Limited company (AS) Aurskog-Høland Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 7.5m
Operating profit NOK 583,000
Equity NOK 861,000
Incorporated 2024
Share capital NOK 30,000

TTN ENTREPRENØR AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 933861384. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Totalentreprise innen bygg og anlegg, nyoppføring og rehabilitering av alle type bygg og annet som naturlig hører innunder en slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.5m in revenue and NOK 583,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.5m
Operating profit
NOK 583,000
Equity
NOK 861,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns TTN ENTREPRENØR AS?

THORBJØRN TRAAHOLT NILSEN
TTN ENTREPRENØR AS
NOK 7.5m rev. · NOK 583,000 profit

TTN ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TTN ENTREPRENØR AS

Who owns TTN ENTREPRENØR AS?

THORBJØRN TRAAHOLT NILSEN is the largest registered owner, with 100.0%.

What is the revenue of TTN ENTREPRENØR AS?

TTN ENTREPRENØR AS had revenue of NOK 7.5m in 2025.

Who is the general manager of TTN ENTREPRENØR AS?

Thorbjørn Traaholt Nilsen is registered as general manager of TTN ENTREPRENØR AS.

Where is TTN ENTREPRENØR AS based?

TTN ENTREPRENØR AS has its business address in Aurskog.

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.