biztrac. BETA
COMPANY REGISTER PROFILE
988196312 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

NT LAST OG BUSS AS

Org. no. 988196312 Limited company (AS) Steinkjer Incorporated 2005 Active
Revenue 2025 NOK 19.8m
Operating profit NOK 321,000
Equity NOK 2.0m
Incorporated 2005
Employees 8
Share capital NOK 1.1m

NT LAST OG BUSS AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 988196312. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2005 and has 8 registered employees. Registered share capital is NOK 1.1m, divided into 1060 shares. The company's stated purpose is: “Handel og reparasjoner av kjøretøyer samt annen virksomhet som naturlig står i forbindelse med dette. Og å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.8m in revenue and NOK 321,000 in operating profit.

Key figures · 2025

Revenue
NOK 19.8m
▼ −8 %
Operating profit
NOK 321,000
▼ −52 %
Equity
NOK 2.0m
▲ +2 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns NT LAST OG BUSS AS?

NT LAST OG BUSS AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about NT LAST OG BUSS AS

Who owns NT LAST OG BUSS AS?

Stig Arve Reierskog is the largest registered owner, with 37.7%.

What is the revenue of NT LAST OG BUSS AS?

NT LAST OG BUSS AS had revenue of NOK 19.8m in 2025.

Who is the general manager of NT LAST OG BUSS AS?

Stig Arve Reierskog is registered as general manager of NT LAST OG BUSS AS.

Where is NT LAST OG BUSS AS based?

NT LAST OG BUSS AS has its business address in Steinkjer.

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.