BIZTRAC BETA
Business and other management consultancy activities

GODFOTEN RÅDGIVING AS

Org. no. 834987872 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 1.2m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

GODFOTEN RÅDGIVING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 834987872. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 1.2m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns GODFOTEN RÅDGIVING AS?

TONY CHRISTIAN TILLER
GODFOTEN RÅDGIVING AS
· NOK −2,000 profit

GODFOTEN RÅDGIVING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GODFOTEN RÅDGIVING AS own?

GODFOTEN RÅDGIVING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GODFOTEN RÅDGIVING AS

Who owns GODFOTEN RÅDGIVING AS?

TONY CHRISTIAN TILLER is the largest registered owner, with 100.0%.

Who is the general manager of GODFOTEN RÅDGIVING AS?

Tony Christian Tiller is registered as general manager of GODFOTEN RÅDGIVING AS.

Where is GODFOTEN RÅDGIVING AS based?

GODFOTEN RÅDGIVING AS has its business address in Skedsmokorset.

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.