BIZTRAC BETA
Rental and operating of own or leased real estate

TØNSÅSEN N2 AS

Org. no. 912135004 Limited company (AS) Stjørdal Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 413,000
Operating profit NOK 386,000
Equity NOK 1.8m
Incorporated 2013
Share capital NOK 300,000

Signals

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

TØNSÅSEN N2 AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 912135004. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Utvikling og utleie av eiendom, samt annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 413,000 in revenue and NOK 386,000 in operating profit.

Key figures · 2024

Revenue
NOK 413,000
Operating profit
NOK 386,000
Equity
NOK 1.8m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns TØNSÅSEN N2 AS?

TVERÅS HOLDING AS
TØNSÅSEN N2 AS
NOK 413,000 rev. · NOK 386,000 profit

TØNSÅSEN N2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØNSÅSEN N2 AS

Who owns TØNSÅSEN N2 AS?

TVERÅS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TØNSÅSEN N2 AS?

TØNSÅSEN N2 AS had revenue of NOK 413,000 in 2024.

Who is the general manager of TØNSÅSEN N2 AS?

Frode Tverås is registered as general manager of TØNSÅSEN N2 AS.

Where is TØNSÅSEN N2 AS based?

TØNSÅSEN N2 AS has its business address in Stjørdal.

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.